Re: [Y2038] [RFC PATCH] y2038: __get_old_timespec32() can be static
From: Arnd Bergmann <arnd@arndb.de>
Date: 2018-08-29 13:17:55
Also in:
linux-api, lkml
On Wed, Aug 29, 2018 at 2:52 PM kbuild test robot [off-list ref] wrote:
quoted hunk ↗ jump to hunk
Fixes: ee16c8f415e4 ("y2038: Globally rename compat_time to old_time32") Signed-off-by: kbuild test robot <redacted> --- time.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)diff --git a/kernel/time/time.c b/kernel/time/time.c index f1983f4..e3a7f7f 100644 --- a/kernel/time/time.c +++ b/kernel/time/time.c@@ -863,7 +863,7 @@ int put_timespec64(const struct timespec64 *ts, } EXPORT_SYMBOL_GPL(put_timespec64); -int __get_old_timespec32(struct timespec64 *ts64, +static int __get_old_timespec32(struct timespec64 *ts64, const struct old_timespec32 __user *cts) {
This was caused by an older patch and we already get the same
warning in mainline linux, the bot triggered again after I renamed
it. Anyway, the fix is good, and I'll come up with a proper changelog
to include it in my series.
Arnd