linux-next: build warnings after merge of the rr tree
in [Kernel]
|
Prev: [PATCH] powerpc: remove unused 'protect4gb' boot parameter
Next: [PATCH 2/2 V2] hwmon: (coretemp) Get TjMax value from MSR
From: Stephen Rothwell on 9 May 2010 23:50 Hi Rusty, On Mon, 10 May 2010 13:44:09 +1000 Stephen Rothwell <sfr(a)canb.auug.org.au> wrote: > > drivers/acpi/debug.c:141: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type > include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' > > Introduced by commit a1c3b92923eced4ee034fa15bf058f91e435e08c ("param:param_ops"). Also drivers/message/fusion/mptbase.c:112: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' drivers/message/fusion/mptbase.c:112: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' drivers/message/fusion/mptbase.c:112: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' drivers/message/fusion/mptbase.c:112: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Rusty Russell on 10 May 2010 08:40 On Mon, 10 May 2010 01:16:20 pm Stephen Rothwell wrote: > Hi Rusty, > > On Mon, 10 May 2010 13:44:09 +1000 Stephen Rothwell <sfr(a)canb.auug.org.au> wrote: > > > > drivers/acpi/debug.c:141: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type > > include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' > > > > Introduced by commit a1c3b92923eced4ee034fa15bf058f91e435e08c ("param:param_ops"). > > Also > > drivers/message/fusion/mptbase.c:112: warning: passing argument 1 of '__check_old_set_param' from incompatible pointer type > include/linux/moduleparam.h:165: note: expected 'int (*)(const char *, struct kernel_param *)' but argument is of type 'int (*)(const char *, const struct kernel_param *)' Thanks, these are harmless, and I had followup patches outside linux-next which resolve them. I've now included them in the linux-next part of the series. Thanks, Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Stephen Rothwell on 10 May 2010 12:00
Hi Rusty, On Mon, 10 May 2010 22:03:53 +0930 Rusty Russell <rusty(a)rustcorp.com.au> wrote: > > Thanks, these are harmless, and I had followup patches outside linux-next > which resolve them. > > I've now included them in the linux-next part of the series. Excellent, thanks. The problem with "harmless" warnings is that they make the important warnings harder to spot. :-( -- Cheers, Stephen Rothwell sfr(a)canb.auug.org.au http://www.canb.auug.org.au/~sfr/ |