Skip to content

Commit 743f5cd

Browse files
kbuild test robotarndb
authored andcommitted
y2038: __get_old_timespec32() can be static
The kbuild test robot reports two new warnings with the previous patch: 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? These are actually older bugs, but came up now after the symbol got renamed. Fortunately, commit afef05c ("time: Enable get/put_compat_itimerspec64 always") makes the two functions (__compat_get_timespec64/__compat_get_timespec64) local to time.c already, so we can mark them as 'static'. Fixes: ee16c8f ("y2038: Globally rename compat_time to old_time32") Signed-off-by: kbuild test robot <fengguang.wu@intel.com> [arnd: added changelog text] Signed-off-by: Arnd Bergmann <arnd@arndb.de>
1 parent 9afc5ee commit 743f5cd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

kernel/time/time.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -863,7 +863,7 @@ int put_timespec64(const struct timespec64 *ts,
863863
}
864864
EXPORT_SYMBOL_GPL(put_timespec64);
865865

866-
int __get_old_timespec32(struct timespec64 *ts64,
866+
static int __get_old_timespec32(struct timespec64 *ts64,
867867
const struct old_timespec32 __user *cts)
868868
{
869869
struct old_timespec32 ts;
@@ -879,7 +879,7 @@ int __get_old_timespec32(struct timespec64 *ts64,
879879
return 0;
880880
}
881881

882-
int __put_old_timespec32(const struct timespec64 *ts64,
882+
static int __put_old_timespec32(const struct timespec64 *ts64,
883883
struct old_timespec32 __user *cts)
884884
{
885885
struct old_timespec32 ts = {

0 commit comments

Comments
 (0)