[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <201808292023.n7IP8zK3%fengguang.wu@intel.com>
Date: Wed, 29 Aug 2018 20:50:51 +0800
From: kbuild test robot <lkp@...el.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: kbuild-all@...org, tglx@...utronix.de, y2038@...ts.linaro.org,
linux-api@...r.kernel.org, Christoph Hellwig <hch@....de>,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
deepa.kernel@...il.com, linux-arch@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH 03/14] y2038: Globally rename compat_time to old_time32
Hi Arnd,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc1 next-20180829]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/y2038-syscall-changes-for-4-20/20180828-035049
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
include/uapi/linux/perf_event.h:147:56: sparse: cast truncates bits from constant value (8000000000000000 becomes 0)
>> kernel/time/time.c:866:5: sparse: symbol '__get_old_timespec32' was not declared. Should it be static?
>> kernel/time/time.c:882:5: sparse: symbol '__put_old_timespec32' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists