Re: linux-next: build failure after merge of the staging tree

From: Greg KH
Date: Tue Mar 10 2015 - 11:08:27 EST


On Tue, Mar 10, 2015 at 04:07:28PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> After merging the staging tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from include/linux/module.h:17:0,
> from drivers/staging/sm750fb/sm750.c:2:
> drivers/staging/sm750fb/sm750.c: In function '__check_g_option':
> drivers/staging/sm750fb/sm750.c:1436:14: error: 'g_option' undeclared (first use in this function)
> module_param(g_option,charp,S_IRUGO);
> ^
>
> Caused by commit 81dee67e215b ("staging: sm750fb: add sm750 to staging").
>
> This driver also produced a large number of warnings ... a lot like this:
>
> drivers/staging/sm750fb/sm750.c: In function 'lynxfb_ops_mmap':
> drivers/staging/sm750fb/sm750.c:533:2: warning: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'long unsigned int' [-Wformat=]
> printk("lynxfb mmap pgoff: %x\n", vma->vm_pgoff);
> ^
>
> Also note:
>
> In file included from drivers/staging/sm750fb/ddk750_mode.h:4:0,
> from drivers/staging/sm750fb/ddk750.h:15,
> from drivers/staging/sm750fb/sm750_hw.c:24:
> drivers/staging/sm750fb/ddk750_chip.h:4:0: warning: "SM750LE_REVISION_ID" redefined
> #define SM750LE_REVISION_ID (char)0xfe
> ^
> In file included from drivers/staging/sm750fb/sm750_hw.c:23:0:
> drivers/staging/sm750fb/sm750_hw.h:8:0: note: this is the location of the previous definition
> #define SM750LE_REVISION_ID (unsigned char)0xfe
> ^
>
> I have disabled this driver for now, please let me know when it is OK
> to enable it again.

Sorry about that. Yes, I know it's a mess. The build error on ppc
should now be fixed in my tree. The build warnings are still there
(some are gone). I should just go fix them up myself, and will do so
tonight if I don't get a patch from someone else that does so first...

So it should be safe to enable again.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/