m68knommu: fix sparse warnings in signal code
authorGreg Ungerer <gerg@linux-m68k.org>
Tue, 15 Sep 2020 05:16:49 +0000 (15:16 +1000)
committerGreg Ungerer <gerg@linux-m68k.org>
Mon, 5 Oct 2020 11:51:31 +0000 (21:51 +1000)
commit006967471c8b6ba382afc65222e25a283449a3e8
treec07fdc2b66d320d0b8e2b35467d96a8012d8343c
parenta27bc11f4b7c54a95a977a8e8b15c84dac804bd4
m68knommu: fix sparse warnings in signal code

Commit 858b810bf63f ("m68knommu: switch to using asm-generic/uaccess.h")
cleaned up a number of sparse warnings associated with lack of __user
annotations. It also uncovered a couple of more in the signal handling
code:

arch/m68k/kernel/signal.c:923:16:    expected char [noderef] __user *__x
arch/m68k/kernel/signal.c:923:16:    got void *
arch/m68k/kernel/signal.c:1007:16: warning: incorrect type in initializer (different address spaces)
arch/m68k/kernel/signal.c:1007:16:    expected char [noderef] __user *__x
arch/m68k/kernel/signal.c:1007:16:    got void *
arch/m68k/kernel/signal.c:1132:6: warning: symbol 'do_notify_resume' was not declared. Should it be static?

These are specific to a non-MMU configuration. Fix these inserting the
correct __user annotations as required.

Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
arch/m68k/kernel/signal.c