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

From: Stephen Rothwell Date: Tue, 23 Jun 2020 13:51:34 +1000 > I have added the following merge fix patch. > > From: Stephen Rothwell > Date: Tue, 23 Jun 2020 13:43:06 +1000 > Subject: [PATCH] net/core/devlink.c: remove new uninitialized_var() usage > > Signed-off-by: Stephen Rothwell

linux-next: build failure after merge of the kspp tree

Hi all, After merging the kspp tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: net/core/devlink.c: In function 'devlink_nl_port_function_attrs_put': net/core/devlink.c:586:3: warning: parameter names (without types) in function declaration 586 | int

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

On Sun, Jun 21, 2020 at 11:48:51PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 allnoconfig) > failed like this: > > x86_64-linux-gnu-ld: fs/file.o: in function `__fd_install_received': > file.c:(.text+0x1010): undefined reference to

linux-next: build failure after merge of the kspp tree

Hi all, After merging the kspp tree, today's linux-next build (x86_64 allnoconfig) failed like this: x86_64-linux-gnu-ld: fs/file.o: in function `__fd_install_received': file.c:(.text+0x1010): undefined reference to `sock_from_file' x86_64-linux-gnu-ld: file.c:(.text+0x104a): undefined reference

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

Hi Will, On Tue, 31 Jul 2018 11:09:18 +0100 Will Deacon wrote: > > I've pushed out Laura's fix to the arm64 for-next/core branch, so this > should be resolved in the next next. Thanks. I actually applied Laura's patch to today's linux-next as well. -- Cheers, Stephen Rothwell

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

Hi Will, On Tue, 31 Jul 2018 11:09:18 +0100 Will Deacon wrote: > > I've pushed out Laura's fix to the arm64 for-next/core branch, so this > should be resolved in the next next. Thanks. I actually applied Laura's patch to today's linux-next as well. -- Cheers, Stephen Rothwell

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

On Mon, Jul 30, 2018 at 05:33:56PM +1000, Stephen Rothwell wrote: > On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: > > Thanks, Stephen. I managed to reproduce this by merging for-next/kspp from > > Kees's tree and for-next/core from the arm64 tree. The failure happens when > > building the

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

On Mon, Jul 30, 2018 at 05:33:56PM +1000, Stephen Rothwell wrote: > On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: > > Thanks, Stephen. I managed to reproduce this by merging for-next/kspp from > > Kees's tree and for-next/core from the arm64 tree. The failure happens when > > building the

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

Hi Laura, On Mon, Jul 30, 2018 at 07:47:52AM -0700, Laura Abbott wrote: > On 07/30/2018 12:33 AM, Stephen Rothwell wrote: > >On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: > >>On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > >>>Actually, it may have been caused by

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

Hi Laura, On Mon, Jul 30, 2018 at 07:47:52AM -0700, Laura Abbott wrote: > On 07/30/2018 12:33 AM, Stephen Rothwell wrote: > >On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: > >>On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > >>>Actually, it may have been caused by

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

On 07/30/2018 12:33 AM, Stephen Rothwell wrote: Hi all, On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell wrote: On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell

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

On 07/30/2018 12:33 AM, Stephen Rothwell wrote: Hi all, On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell wrote: On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell

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

Hi all, On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: > > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > > wrote: > > > > > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > > > wrote: > > > > > >

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

Hi all, On Fri, 27 Jul 2018 13:55:22 +0100 Will Deacon wrote: > > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > > wrote: > > > > > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > > > wrote: > > > > > >

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

On Fri, Jul 27, 2018 at 6:27 AM, Will Deacon wrote: > On Fri, Jul 27, 2018 at 02:01:06PM +0100, Will Deacon wrote: >> On Fri, Jul 27, 2018 at 01:55:22PM +0100, Will Deacon wrote: >> > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: >> > > On Fri, 27 Jul 2018 19:06:47 +1000

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

On Fri, Jul 27, 2018 at 6:27 AM, Will Deacon wrote: > On Fri, Jul 27, 2018 at 02:01:06PM +0100, Will Deacon wrote: >> On Fri, Jul 27, 2018 at 01:55:22PM +0100, Will Deacon wrote: >> > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: >> > > On Fri, 27 Jul 2018 19:06:47 +1000

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

On Fri, Jul 27, 2018 at 02:01:06PM +0100, Will Deacon wrote: > On Fri, Jul 27, 2018 at 01:55:22PM +0100, Will Deacon wrote: > > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > > > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > > > wrote: > > > > > > > > On Fri, 27 Jul

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

On Fri, Jul 27, 2018 at 02:01:06PM +0100, Will Deacon wrote: > On Fri, Jul 27, 2018 at 01:55:22PM +0100, Will Deacon wrote: > > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > > > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > > > wrote: > > > > > > > > On Fri, 27 Jul

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

On Fri, Jul 27, 2018 at 01:55:22PM +0100, Will Deacon wrote: > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > > wrote: > > > > > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > > > wrote: > > > > > > > > After

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

On Fri, Jul 27, 2018 at 01:55:22PM +0100, Will Deacon wrote: > On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > > wrote: > > > > > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > > > wrote: > > > > > > > > After

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

On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > wrote: > > > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > > wrote: > > > > > > After merging the kspp tree, today's linux-next build (x86_64 > > > allmodconfig)

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

On Fri, Jul 27, 2018 at 08:55:11PM +1000, Stephen Rothwell wrote: > On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell > wrote: > > > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > > wrote: > > > > > > After merging the kspp tree, today's linux-next build (x86_64 > > > allmodconfig)

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

Hi all, On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell wrote: > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > wrote: > > > > After merging the kspp tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > cc1: error: plugin stackleak_plugin should be

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

Hi all, On Fri, 27 Jul 2018 19:06:47 +1000 Stephen Rothwell wrote: > > On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell > wrote: > > > > After merging the kspp tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > cc1: error: plugin stackleak_plugin should be

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

Hi all, On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell wrote: > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > cc1: error: plugin stackleak_plugin should be specified before > -fplugin-arg-stackleak_plugin-disable in the command line

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

Hi all, On Fri, 27 Jul 2018 19:02:07 +1000 Stephen Rothwell wrote: > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > cc1: error: plugin stackleak_plugin should be specified before > -fplugin-arg-stackleak_plugin-disable in the command line

linux-next: build failure after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: cc1: error: plugin stackleak_plugin should be specified before -fplugin-arg-stackleak_plugin-disable in the command line Maybe caused by commit a8b9eaddb9c0 ("gcc-plugins: Add STACKLEAK

linux-next: build failure after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: cc1: error: plugin stackleak_plugin should be specified before -fplugin-arg-stackleak_plugin-disable in the command line Maybe caused by commit a8b9eaddb9c0 ("gcc-plugins: Add STACKLEAK

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

On Wed, Nov 8, 2017 at 4:18 PM, Darrick J. Wong wrote: > Agreed. I guess we'll see you for round X when you get to general > kmalloc annotating. :) That should be "fun". :) -Kees -- Kees Cook Pixel Security

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

On Wed, Nov 8, 2017 at 4:18 PM, Darrick J. Wong wrote: > Agreed. I guess we'll see you for round X when you get to general > kmalloc annotating. :) That should be "fun". :) -Kees -- Kees Cook Pixel Security

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

On Wed, Nov 08, 2017 at 03:43:47PM -0800, Kees Cook wrote: > On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell > wrote: > > Hi Kees, > > > > After merging the kspp tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from

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

On Wed, Nov 08, 2017 at 03:43:47PM -0800, Kees Cook wrote: > On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell > wrote: > > Hi Kees, > > > > After merging the kspp tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > In file included from

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

On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell wrote: > Hi Kees, > > After merging the kspp tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/compiler_types.h:58:0, > from

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

On Tue, Nov 7, 2017 at 9:23 PM, Stephen Rothwell wrote: > Hi Kees, > > After merging the kspp tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/compiler_types.h:58:0, > from include/uapi/linux/stddef.h:2, >

linux-next: build failure after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/compiler_types.h:58:0, from include/uapi/linux/stddef.h:2, from include/linux/stddef.h:5, from

linux-next: build failure after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/compiler_types.h:58:0, from include/uapi/linux/stddef.h:2, from include/linux/stddef.h:5, from

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

On Tue, 27 Jun 2017, Kees Cook wrote: > On Mon, Jun 26, 2017 at 8:33 PM, James Morris wrote: > > On Mon, 26 Jun 2017, Kees Cook wrote: > > > >> >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using > >> >> labels") > >> >> Signed-off-by: Stephen Rothwell

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

On Tue, 27 Jun 2017, Kees Cook wrote: > On Mon, Jun 26, 2017 at 8:33 PM, James Morris wrote: > > On Mon, 26 Jun 2017, Kees Cook wrote: > > > >> >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using > >> >> labels") > >> >> Signed-off-by: Stephen Rothwell > >> > Acked-by: John

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

On Mon, Jun 26, 2017 at 8:33 PM, James Morris wrote: > On Mon, 26 Jun 2017, Kees Cook wrote: > >> >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using labels") >> >> Signed-off-by: Stephen Rothwell >> > Acked-by: John Johansen

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

On Mon, Jun 26, 2017 at 8:33 PM, James Morris wrote: > On Mon, 26 Jun 2017, Kees Cook wrote: > >> >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using labels") >> >> Signed-off-by: Stephen Rothwell >> > Acked-by: John Johansen >> >> Hi James, >> >> Just a ping; this needs to get

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

On Mon, 26 Jun 2017, Kees Cook wrote: > >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using labels") > >> Signed-off-by: Stephen Rothwell > > Acked-by: John Johansen > > Hi James, > > Just a ping; this needs to get into

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

On Mon, 26 Jun 2017, Kees Cook wrote: > >> Fixes: 8014370f1257 ("apparmor: move path_link mediation to using labels") > >> Signed-off-by: Stephen Rothwell > > Acked-by: John Johansen > > Hi James, > > Just a ping; this needs to get into -next to avoid build errors. Surely Linus will resolve

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

On Mon, Jun 19, 2017 at 10:39 PM, John Johansen wrote: > On 06/19/2017 09:56 PM, Stephen Rothwell wrote: >> Hi all, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> security/apparmor/file.c: In function

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

On Mon, Jun 19, 2017 at 10:39 PM, John Johansen wrote: > On 06/19/2017 09:56 PM, Stephen Rothwell wrote: >> Hi all, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> security/apparmor/file.c: In function 'aa_path_link': >>

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

On 06/19/2017 10:39 PM, Kees Cook wrote: > On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell > wrote: >> Hi all, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> security/apparmor/file.c: In function

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

On 06/19/2017 10:39 PM, Kees Cook wrote: > On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell > wrote: >> Hi all, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> security/apparmor/file.c: In function 'aa_path_link': >>

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

On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error:

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

On Mon, Jun 19, 2017 at 9:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error: positional initialization of

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

On 06/19/2017 09:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error: positional initialization of field in

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

On 06/19/2017 09:56 PM, Stephen Rothwell wrote: > Hi all, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > security/apparmor/file.c: In function 'aa_path_link': > security/apparmor/file.c:475:23: error: positional initialization of field in

linux-next: build failure after merge of the kspp tree

Hi all, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: security/apparmor/file.c: In function 'aa_path_link': security/apparmor/file.c:475:23: error: positional initialization of field in 'struct' declared with 'designated_init' attribute

linux-next: build failure after merge of the kspp tree

Hi all, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: security/apparmor/file.c: In function 'aa_path_link': security/apparmor/file.c:475:23: error: positional initialization of field in 'struct' declared with 'designated_init' attribute

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

On Sun, Jun 18, 2017 at 5:23 PM, Stephen Rothwell wrote: > Hi Stephen, > > On Fri, 16 Jun 2017 13:31:44 +1000 Stephen Rothwell > wrote: >> >> Hi Kees, >> >> On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: >> > >> > I'm so

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

On Sun, Jun 18, 2017 at 5:23 PM, Stephen Rothwell wrote: > Hi Stephen, > > On Fri, 16 Jun 2017 13:31:44 +1000 Stephen Rothwell > wrote: >> >> Hi Kees, >> >> On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: >> > >> > I'm so confused -- isn't this in next? All the build tests I did were >> >

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

Hi Stephen, On Fri, 16 Jun 2017 13:31:44 +1000 Stephen Rothwell wrote: > > Hi Kees, > > On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: > > > > I'm so confused -- isn't this in next? All the build tests I did were > > against yesterday's -next

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

Hi Stephen, On Fri, 16 Jun 2017 13:31:44 +1000 Stephen Rothwell wrote: > > Hi Kees, > > On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: > > > > I'm so confused -- isn't this in next? All the build tests I did were > > against yesterday's -next which includes this from what I can see...

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

Hi Kees, On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: > > I'm so confused -- isn't this in next? All the build tests I did were > against yesterday's -next which includes this from what I can see... It is in next, but gets merged after the kspp tree ... so, this is

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

Hi Kees, On Thu, 15 Jun 2017 20:20:47 -0700 Kees Cook wrote: > > I'm so confused -- isn't this in next? All the build tests I did were > against yesterday's -next which includes this from what I can see... It is in next, but gets merged after the kspp tree ... so, this is when inter-tree

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

On Thu, Jun 15, 2017 at 7:51 PM, Daniel Micay wrote: > On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote: >> Hi Kees, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> In file included from

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

On Thu, Jun 15, 2017 at 7:51 PM, Daniel Micay wrote: > On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote: >> Hi Kees, >> >> After merging the kspp tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> In file included from include/linux/bitmap.h:8:0, >>

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

> https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/ in the > 4.13/scsi-queue and for-next branches. I think that's why Kees didn't > include it but I get he needs to add that. s/get/guess/ Or is that repo supposed to get pulled into next?

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

> https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/ in the > 4.13/scsi-queue and for-next branches. I think that's why Kees didn't > include it but I get he needs to add that. s/get/guess/ Or is that repo supposed to get pulled into next?

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

On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote: > Hi Kees, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/bitmap.h:8:0, > from include/linux/cpumask.h:11, >

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

On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote: > Hi Kees, > > After merging the kspp tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/bitmap.h:8:0, > from include/linux/cpumask.h:11, >

linux-next: build failure after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/bitmap.h:8:0, from include/linux/cpumask.h:11, from arch/x86/include/asm/cpumask.h:4, from

linux-next: build failure after merge of the kspp tree

Hi Kees, After merging the kspp tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/bitmap.h:8:0, from include/linux/cpumask.h:11, from arch/x86/include/asm/cpumask.h:4, from