public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
* linux-next: build failures after merge of the staging tree
@ 2021-01-04  1:26 Stephen Rothwell
  2021-01-04  8:27 ` Geert Uytterhoeven
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2021-01-04  1:26 UTC (permalink / raw)
  To: Greg KH; +Cc: Song Chen, Linux Kernel Mailing List, Linux Next Mailing List

[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]

Hi all,

After merging the staging tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

In file included from include/linux/printk.h:6,
                 from include/linux/kernel.h:16,
                 from drivers/staging/board/kzm9d.c:4:
drivers/staging/board/kzm9d.c:28:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
   28 | device_initcall(kzm9d_init);
      |                 ^~~~~~~~~~
include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
  197 |   __attribute__((__section__(#__sec ".init"))) = fn;
      |                                                  ^~
include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
  229 | #define device_initcall(fn)  __define_initcall(fn, 6)
      |                              ^~~~~~~~~~~~~~~~~
drivers/staging/board/kzm9d.c:28:1: note: in expansion of macro 'device_initcall'
   28 | device_initcall(kzm9d_init);
      | ^~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
In file included from include/linux/printk.h:6,
                 from include/linux/kernel.h:16,
                 from include/asm-generic/bug.h:20,
                 from arch/arm/include/asm/bug.h:60,
                 from include/linux/bug.h:5,
                 from include/linux/thread_info.h:12,
                 from include/asm-generic/current.h:5,
                 from ./arch/arm/include/generated/asm/current.h:1,
                 from include/linux/sched.h:12,
                 from include/linux/ratelimit.h:6,
                 from include/linux/dev_printk.h:16,
                 from include/linux/device.h:15,
                 from include/linux/dma-mapping.h:7,
                 from drivers/staging/board/armadillo800eva.c:12:
drivers/staging/board/armadillo800eva.c:90:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
   90 | device_initcall(armadillo800eva_init);
      |                 ^~~~~~~~~~~~~~~~~~~~
include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
  197 |   __attribute__((__section__(#__sec ".init"))) = fn;
      |                                                  ^~
include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
  229 | #define device_initcall(fn)  __define_initcall(fn, 6)
      |                              ^~~~~~~~~~~~~~~~~
drivers/staging/board/armadillo800eva.c:90:1: note: in expansion of macro 'device_initcall'
   90 | device_initcall(armadillo800eva_init);
      | ^~~~~~~~~~~~~~~

Caused by commit

  850c35bb28ec ("staging: board: Remove macro board_staging")

I have used the staging tree from next-20201223 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: build failures after merge of the staging tree
  2021-01-04  1:26 linux-next: build failures after merge of the staging tree Stephen Rothwell
@ 2021-01-04  8:27 ` Geert Uytterhoeven
  2021-01-04  8:32   ` chensong_2000
  2021-01-04 14:56   ` Greg KH
  0 siblings, 2 replies; 4+ messages in thread
From: Geert Uytterhoeven @ 2021-01-04  8:27 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Greg KH, Song Chen, Linux Kernel Mailing List,
	Linux Next Mailing List

On Mon, Jan 4, 2021 at 6:12 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> After merging the staging tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> In file included from include/linux/printk.h:6,
>                  from include/linux/kernel.h:16,
>                  from drivers/staging/board/kzm9d.c:4:
> drivers/staging/board/kzm9d.c:28:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
>    28 | device_initcall(kzm9d_init);
>       |                 ^~~~~~~~~~
> include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
>   197 |   __attribute__((__section__(#__sec ".init"))) = fn;
>       |                                                  ^~
> include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
>   229 | #define device_initcall(fn)  __define_initcall(fn, 6)
>       |                              ^~~~~~~~~~~~~~~~~
> drivers/staging/board/kzm9d.c:28:1: note: in expansion of macro 'device_initcall'
>    28 | device_initcall(kzm9d_init);
>       | ^~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
> In file included from include/linux/printk.h:6,
>                  from include/linux/kernel.h:16,
>                  from include/asm-generic/bug.h:20,
>                  from arch/arm/include/asm/bug.h:60,
>                  from include/linux/bug.h:5,
>                  from include/linux/thread_info.h:12,
>                  from include/asm-generic/current.h:5,
>                  from ./arch/arm/include/generated/asm/current.h:1,
>                  from include/linux/sched.h:12,
>                  from include/linux/ratelimit.h:6,
>                  from include/linux/dev_printk.h:16,
>                  from include/linux/device.h:15,
>                  from include/linux/dma-mapping.h:7,
>                  from drivers/staging/board/armadillo800eva.c:12:
> drivers/staging/board/armadillo800eva.c:90:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
>    90 | device_initcall(armadillo800eva_init);
>       |                 ^~~~~~~~~~~~~~~~~~~~
> include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
>   197 |   __attribute__((__section__(#__sec ".init"))) = fn;
>       |                                                  ^~
> include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
>   229 | #define device_initcall(fn)  __define_initcall(fn, 6)
>       |                              ^~~~~~~~~~~~~~~~~
> drivers/staging/board/armadillo800eva.c:90:1: note: in expansion of macro 'device_initcall'
>    90 | device_initcall(armadillo800eva_init);
>       | ^~~~~~~~~~~~~~~
>
> Caused by commit
>
>   850c35bb28ec ("staging: board: Remove macro board_staging")
>
> I have used the staging tree from next-20201223 for today.

Note that a similar patch was (IMHO rightfully) rejected 3 years ago:
https://lore.kernel.org/lkml/20170220175506.GA30142@kroah.com/

So please drop it. Thanks!

Gr{oetje,eeting}s,

                        Geert


--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: build failures after merge of the staging tree
  2021-01-04  8:27 ` Geert Uytterhoeven
@ 2021-01-04  8:32   ` chensong_2000
  2021-01-04 14:56   ` Greg KH
  1 sibling, 0 replies; 4+ messages in thread
From: chensong_2000 @ 2021-01-04  8:32 UTC (permalink / raw)
  To: Geert Uytterhoeven, Stephen Rothwell
  Cc: Greg KH, Linux Kernel Mailing List, Linux Next Mailing List

i will take care of this

在 2021/1/4 下午4:27, Geert Uytterhoeven 写道:
> On Mon, Jan 4, 2021 at 6:12 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>> After merging the staging tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> In file included from include/linux/printk.h:6,
>>                   from include/linux/kernel.h:16,
>>                   from drivers/staging/board/kzm9d.c:4:
>> drivers/staging/board/kzm9d.c:28:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
>>     28 | device_initcall(kzm9d_init);
>>        |                 ^~~~~~~~~~
>> include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
>>    197 |   __attribute__((__section__(#__sec ".init"))) = fn;
>>        |                                                  ^~
>> include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
>>    229 | #define device_initcall(fn)  __define_initcall(fn, 6)
>>        |                              ^~~~~~~~~~~~~~~~~
>> drivers/staging/board/kzm9d.c:28:1: note: in expansion of macro 'device_initcall'
>>     28 | device_initcall(kzm9d_init);
>>        | ^~~~~~~~~~~~~~~
>> cc1: some warnings being treated as errors
>> In file included from include/linux/printk.h:6,
>>                   from include/linux/kernel.h:16,
>>                   from include/asm-generic/bug.h:20,
>>                   from arch/arm/include/asm/bug.h:60,
>>                   from include/linux/bug.h:5,
>>                   from include/linux/thread_info.h:12,
>>                   from include/asm-generic/current.h:5,
>>                   from ./arch/arm/include/generated/asm/current.h:1,
>>                   from include/linux/sched.h:12,
>>                   from include/linux/ratelimit.h:6,
>>                   from include/linux/dev_printk.h:16,
>>                   from include/linux/device.h:15,
>>                   from include/linux/dma-mapping.h:7,
>>                   from drivers/staging/board/armadillo800eva.c:12:
>> drivers/staging/board/armadillo800eva.c:90:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
>>     90 | device_initcall(armadillo800eva_init);
>>        |                 ^~~~~~~~~~~~~~~~~~~~
>> include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
>>    197 |   __attribute__((__section__(#__sec ".init"))) = fn;
>>        |                                                  ^~
>> include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
>>    229 | #define device_initcall(fn)  __define_initcall(fn, 6)
>>        |                              ^~~~~~~~~~~~~~~~~
>> drivers/staging/board/armadillo800eva.c:90:1: note: in expansion of macro 'device_initcall'
>>     90 | device_initcall(armadillo800eva_init);
>>        | ^~~~~~~~~~~~~~~
>>
>> Caused by commit
>>
>>    850c35bb28ec ("staging: board: Remove macro board_staging")
>>
>> I have used the staging tree from next-20201223 for today.
> 
> Note that a similar patch was (IMHO rightfully) rejected 3 years ago:
> https://lore.kernel.org/lkml/20170220175506.GA30142@kroah.com/
> 
> So please drop it. Thanks!
> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                  -- Linus Torvalds
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: build failures after merge of the staging tree
  2021-01-04  8:27 ` Geert Uytterhoeven
  2021-01-04  8:32   ` chensong_2000
@ 2021-01-04 14:56   ` Greg KH
  1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2021-01-04 14:56 UTC (permalink / raw)
  To: Geert Uytterhoeven
  Cc: Stephen Rothwell, Song Chen, Linux Kernel Mailing List,
	Linux Next Mailing List

On Mon, Jan 04, 2021 at 09:27:01AM +0100, Geert Uytterhoeven wrote:
> On Mon, Jan 4, 2021 at 6:12 AM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > After merging the staging tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > In file included from include/linux/printk.h:6,
> >                  from include/linux/kernel.h:16,
> >                  from drivers/staging/board/kzm9d.c:4:
> > drivers/staging/board/kzm9d.c:28:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
> >    28 | device_initcall(kzm9d_init);
> >       |                 ^~~~~~~~~~
> > include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
> >   197 |   __attribute__((__section__(#__sec ".init"))) = fn;
> >       |                                                  ^~
> > include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
> >   229 | #define device_initcall(fn)  __define_initcall(fn, 6)
> >       |                              ^~~~~~~~~~~~~~~~~
> > drivers/staging/board/kzm9d.c:28:1: note: in expansion of macro 'device_initcall'
> >    28 | device_initcall(kzm9d_init);
> >       | ^~~~~~~~~~~~~~~
> > cc1: some warnings being treated as errors
> > In file included from include/linux/printk.h:6,
> >                  from include/linux/kernel.h:16,
> >                  from include/asm-generic/bug.h:20,
> >                  from arch/arm/include/asm/bug.h:60,
> >                  from include/linux/bug.h:5,
> >                  from include/linux/thread_info.h:12,
> >                  from include/asm-generic/current.h:5,
> >                  from ./arch/arm/include/generated/asm/current.h:1,
> >                  from include/linux/sched.h:12,
> >                  from include/linux/ratelimit.h:6,
> >                  from include/linux/dev_printk.h:16,
> >                  from include/linux/device.h:15,
> >                  from include/linux/dma-mapping.h:7,
> >                  from drivers/staging/board/armadillo800eva.c:12:
> > drivers/staging/board/armadillo800eva.c:90:17: error: initialization of 'initcall_t' {aka 'int (*)(void)'} from incompatible pointer type 'void (*)(void)' [-Werror=incompatible-pointer-types]
> >    90 | device_initcall(armadillo800eva_init);
> >       |                 ^~~~~~~~~~~~~~~~~~~~
> > include/linux/init.h:197:50: note: in definition of macro '___define_initcall'
> >   197 |   __attribute__((__section__(#__sec ".init"))) = fn;
> >       |                                                  ^~
> > include/linux/init.h:229:30: note: in expansion of macro '__define_initcall'
> >   229 | #define device_initcall(fn)  __define_initcall(fn, 6)
> >       |                              ^~~~~~~~~~~~~~~~~
> > drivers/staging/board/armadillo800eva.c:90:1: note: in expansion of macro 'device_initcall'
> >    90 | device_initcall(armadillo800eva_init);
> >       | ^~~~~~~~~~~~~~~
> >
> > Caused by commit
> >
> >   850c35bb28ec ("staging: board: Remove macro board_staging")
> >
> > I have used the staging tree from next-20201223 for today.
> 
> Note that a similar patch was (IMHO rightfully) rejected 3 years ago:
> https://lore.kernel.org/lkml/20170220175506.GA30142@kroah.com/
> 
> So please drop it. Thanks!

Now reverted, thanks.

greg k-h

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-01-04 14:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-01-04  1:26 linux-next: build failures after merge of the staging tree Stephen Rothwell
2021-01-04  8:27 ` Geert Uytterhoeven
2021-01-04  8:32   ` chensong_2000
2021-01-04 14:56   ` Greg KH

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox