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

On Wed, Feb 10, 2021 at 5:37 PM Masahiro Yamada wrote: > > On Wed, Feb 10, 2021 at 5:06 PM Jessica Yu wrote: > > > > +++ Stephen Rothwell [10/02/21 08:50 +1100]: > > >Hi Jessica, > > > > > >On Tue, 9 Feb 2021 16:16:20 +0100 Jessica Yu wrote: > > >> > > >> Hmm, these errors don't look like it's

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

+++ Stephen Rothwell [10/02/21 23:21 +1100]: Hi Jessica, On Wed, 10 Feb 2021 09:06:48 +0100 Jessica Yu wrote: Sorry, by "feature" I meant CONFIG_TRIM_UNUSED_KSYMS. This config option was introduced around v4.7. If simply enabling it produces these compilation errors I was wondering if it

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

Hi Jessica, On Wed, 10 Feb 2021 09:06:48 +0100 Jessica Yu wrote: > > Sorry, by "feature" I meant CONFIG_TRIM_UNUSED_KSYMS. This config > option was introduced around v4.7. If simply enabling it produces > these compilation errors I was wondering if it ever built properly on > powerpc. Ah, of

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

On Wed, Feb 10, 2021 at 5:06 PM Jessica Yu wrote: > > +++ Stephen Rothwell [10/02/21 08:50 +1100]: > >Hi Jessica, > > > >On Tue, 9 Feb 2021 16:16:20 +0100 Jessica Yu wrote: > >> > >> Hmm, these errors don't look like it's related to that particular commit. > >> I was > > > >I found this commit

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

+++ Stephen Rothwell [10/02/21 08:50 +1100]: Hi Jessica, On Tue, 9 Feb 2021 16:16:20 +0100 Jessica Yu wrote: Hmm, these errors don't look like it's related to that particular commit. I was I found this commit by bisection and then tested by reverting it. Before this commit,

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

Hi Jessica, On Tue, 9 Feb 2021 16:16:20 +0100 Jessica Yu wrote: > > Hmm, these errors don't look like it's related to that particular commit. I > was I found this commit by bisection and then tested by reverting it. Before this commit, CONFIG_TRIM_UNUSED_KSYMS would not be set in the

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

On Tue, Feb 09, 2021 at 04:16:20PM +0100, Jessica Yu wrote: > Hmm, these errors don't look like it's related to that particular commit. I > was > able to reproduce these weird autoksym errors even without any modules-next > patches applied, and on a clean v5.11-rc7 tree. I OTOH can't reproduce

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

+++ Stephen Rothwell [09/02/21 21:08 +1100]: Hi all, After merging the modules tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from include/linux/export.h:123, from include/linux/linkage.h:7, from

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

Hi all, After merging the modules tree, today's linux-next build (powerpc allyesconfig) failed like this: In file included from include/linux/export.h:123, from include/linux/linkage.h:7, from arch/powerpc/include/asm/unistd.h:18, from :2:

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

Hi Jessica, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/module.c: In function 'module_enable_x': kernel/module.c:2030:2: error: implicit declaration of function 'frob_text'; did you mean 'rb_next'?

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

Mark Brown writes: > Hi Rusty, > > After merging the modules tree, today's linux-next x86 allmodconfig build > (20151201) failed like this: > > /home/broonie/next/next/arch/x86/kernel/livepatch.c: In function > 'klp_write_module_reloc': >

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

Mark Brown writes: > Hi Rusty, > > After merging the modules tree, today's linux-next x86 allmodconfig build > (20151201) failed like this: > > /home/broonie/next/next/arch/x86/kernel/livepatch.c: In function > 'klp_write_module_reloc': >

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

Hi Rusty, After merging the modules tree, today's linux-next x86 allmodconfig build (20151201) failed like this: /home/broonie/next/next/arch/x86/kernel/livepatch.c: In function 'klp_write_module_reloc': /home/broonie/next/next/arch/x86/kernel/livepatch.c:75:22: error: 'struct module' has no

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

Hi Rusty, After merging the modules tree, today's linux-next x86 allmodconfig build (20151201) failed like this: /home/broonie/next/next/arch/x86/kernel/livepatch.c: In function 'klp_write_module_reloc': /home/broonie/next/next/arch/x86/kernel/livepatch.c:75:22: error: 'struct module' has no

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

Stephen Rothwell writes: > Hi Rusty, > > After merging the modules tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/kexec.h:26:0, > from include/linux/crash_dump.h:5, > from

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/kexec.h:26:0, from include/linux/crash_dump.h:5, from arch/powerpc/platforms/powernv/pci-ioda.c:16:

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/kexec.h:26:0, from include/linux/crash_dump.h:5, from arch/powerpc/platforms/powernv/pci-ioda.c:16:

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

Stephen Rothwell writes: > Hi Rusty, > > After merging the modules tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > In file included from include/linux/kexec.h:26:0, > from include/linux/crash_dump.h:5, >

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

On Thu, Jun 25, 2015 at 2:54 AM, Stephen Rothwell wrote: > Hi Rusty, > > After merging the modules tree, today's linux-next build (powerpc > allnoconfig) failed like this: I promise I'll build with all[no|mod|yes]config next time! ;-) Thanks for catching this one too. > >

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc allnoconfig) failed like this: kernel/params.c:628:6: error: redefinition of 'kernel_param_lock' void kernel_param_lock(struct module *mod) ^ In file included from include/linux/module.h:18:0,

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc allnoconfig) failed like this: kernel/params.c:628:6: error: redefinition of 'kernel_param_lock' void kernel_param_lock(struct module *mod) ^ In file included from include/linux/module.h:18:0,

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

On Thu, Jun 25, 2015 at 2:54 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Rusty, After merging the modules tree, today's linux-next build (powerpc allnoconfig) failed like this: I promise I'll build with all[no|mod|yes]config next time! ;-) Thanks for catching this one too.

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

Hi Dan, On Thu, 25 Jun 2015 08:57:06 +1000 Stephen Rothwell wrote: > > On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman wrote: > > > > On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell > > wrote: > > > > > > After merging the modules tree, today's linux-next build (x86_64 > > > allmodconfig)

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

Hi Dan, On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman wrote: > > On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell > wrote: > > > > After merging the modules tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > that's weird. Are you sure it failed during

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

On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell wrote: > Hi Rusty, > > After merging the modules tree, today's linux-next build (x86_64 > allmodconfig) failed like this: that's weird. Are you sure it failed during allmodconfig? I can see why it would fail like that if CONFIG_MODULES ins't

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

Hi Dan, On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman ddstr...@ieee.org wrote: On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell s...@canb.auug.org.au wrote: After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: that's weird. Are you

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

Hi Dan, On Thu, 25 Jun 2015 08:57:06 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: On Wed, 24 Jun 2015 14:18:44 -0400 Dan Streetman ddstr...@ieee.org wrote: On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell s...@canb.auug.org.au wrote: After merging the modules tree, today's

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

On Tue, Jun 23, 2015 at 9:37 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: that's weird. Are you sure it failed during allmodconfig? I can see why it would fail like that if

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

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/linkage.h:4:0, from include/linux/kernel.h:6, from kernel/params.c:18: kernel/params.c: In function 'param_array':

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

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/linkage.h:4:0, from include/linux/kernel.h:6, from kernel/params.c:18: kernel/params.c: In function 'param_array':

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/params.c: In function 'add_sysfs_param': kernel/params.c:649:9: error: 'struct module_kobject' has no member named 'kp' if ((mk->kp->perm & (S_IWUSR | S_IWGRP | S_IWOTH)) !=

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: kernel/params.c: In function 'add_sysfs_param': kernel/params.c:649:9: error: 'struct module_kobject' has no member named 'kp' if ((mk-kp-perm (S_IWUSR | S_IWGRP | S_IWOTH)) != 0)

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

Hi Rusty, On Thu, 07 Aug 2014 22:37:50 +0930 Rusty Russell wrote: > > Stephen Rothwell writes: > > Hi Rusty, > > > > On Thu, 07 Aug 2014 21:07:20 +0930 Rusty Russell > > wrote: > >> > >> Ah, crap. I really hate that macro magic :( > >> > >> I amended to the minimal fix, so we can pretend

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

Stephen Rothwell writes: > Hi Rusty, > > On Thu, 07 Aug 2014 21:07:20 +0930 Rusty Russell > wrote: >> >> Ah, crap. I really hate that macro magic :( >> >> I amended to the minimal fix, so we can pretend that never happened. > > How about arch/powerpc/platforms/powernv/opal-dump.c as well?

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

Hi Rusty, On Thu, 07 Aug 2014 21:07:20 +0930 Rusty Russell wrote: > > Ah, crap. I really hate that macro magic :( > > I amended to the minimal fix, so we can pretend that never happened. How about arch/powerpc/platforms/powernv/opal-dump.c as well? -- Cheers, Stephen Rothwell

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

Stephen Rothwell writes: > Hi Rusty, > > After merging the modules tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: > > arch/powerpc/platforms/powernv/opal-elog.c:85:28: error: macro "__ATTR_RO" > passed 2 arguments, but takes just 1 > __ATTR_RO(id, elog_id_show);

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

Stephen Rothwell s...@canb.auug.org.au writes: Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/powernv/opal-elog.c:85:28: error: macro __ATTR_RO passed 2 arguments, but takes just 1 __ATTR_RO(id,

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

Hi Rusty, On Thu, 07 Aug 2014 21:07:20 +0930 Rusty Russell ru...@rustcorp.com.au wrote: Ah, crap. I really hate that macro magic :( I amended to the minimal fix, so we can pretend that never happened. How about arch/powerpc/platforms/powernv/opal-dump.c as well? -- Cheers, Stephen

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

Stephen Rothwell s...@canb.auug.org.au writes: Hi Rusty, On Thu, 07 Aug 2014 21:07:20 +0930 Rusty Russell ru...@rustcorp.com.au wrote: Ah, crap. I really hate that macro magic :( I amended to the minimal fix, so we can pretend that never happened. How about

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

Hi Rusty, On Thu, 07 Aug 2014 22:37:50 +0930 Rusty Russell ru...@rustcorp.com.au wrote: Stephen Rothwell s...@canb.auug.org.au writes: Hi Rusty, On Thu, 07 Aug 2014 21:07:20 +0930 Rusty Russell ru...@rustcorp.com.au wrote: Ah, crap. I really hate that macro magic :( I amended

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/powernv/opal-elog.c:85:28: error: macro "__ATTR_RO" passed 2 arguments, but takes just 1 __ATTR_RO(id, elog_id_show); ^

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/powernv/opal-elog.c:85:28: error: macro __ATTR_RO passed 2 arguments, but takes just 1 __ATTR_RO(id, elog_id_show); ^

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

Stephen Rothwell writes: > Hi Rusty, > > After merging the modules tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: Thanks, I've sent off a fix for that file, and asked Stewart for an Ack: Subject: arch/powerpc/platforms/powernv/opal-elog.c: fix world-writable sysfs

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

Stephen Rothwell s...@canb.auug.org.au writes: Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: Thanks, I've sent off a fix for that file, and asked Stewart for an Ack: Subject: arch/powerpc/platforms/powernv/opal-elog.c: fix

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/thread_info.h:11:0, from arch/powerpc/include/asm/ptrace.h:151, from arch/powerpc/include/asm/processor.h:44,

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: In file included from include/linux/thread_info.h:11:0, from arch/powerpc/include/asm/ptrace.h:151, from arch/powerpc/include/asm/processor.h:44,

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

Stephen Rothwell writes: > Hi Rusty, > > After merging the modules tree, today's linux-next build (x86_64 > allmodconfig) failed like this: Hmm, I sent Greg KH a separate patch for staging, which rips these out altogether. He said he'd apply it "in a bit". I see it hasn't hit mainline yet, so

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

Stephen Rothwell s...@canb.auug.org.au writes: Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: Hmm, I sent Greg KH a separate patch for staging, which rips these out altogether. He said he'd apply it in a bit. I see it hasn't hit

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

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/thread_info.h:11:0, from arch/x86/include/asm/preempt.h:6, from include/linux/preempt.h:18, from

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

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/thread_info.h:11:0, from arch/x86/include/asm/preempt.h:6, from include/linux/preempt.h:18, from

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

Stanislaw Gruszka writes: > On Mon, Nov 26, 2012 at 03:10:46PM +1100, Stephen Rothwell wrote: >> After merging the modules tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: >> >> drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: invalid suffix >> "n_disabletype__8"

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

Stanislaw Gruszka sgrus...@redhat.com writes: On Mon, Nov 26, 2012 at 03:10:46PM +1100, Stephen Rothwell wrote: After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: invalid suffix

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

On Mon, Nov 26, 2012 at 03:10:46PM +1100, Stephen Rothwell wrote: > After merging the modules tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: invalid suffix > "n_disabletype__8" on integer constant >

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

On Mon, Nov 26, 2012 at 03:10:46PM +1100, Stephen Rothwell wrote: After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: invalid suffix n_disabletype__8 on integer constant

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

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: invalid suffix "n_disabletype__8" on integer constant drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: expected identifier or

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

Hi Rusty, After merging the modules tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: invalid suffix n_disabletype__8 on integer constant drivers/net/wireless/iwlwifi/iwl-drv.c:1196:1: error: expected identifier or '('

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

Stephen Rothwell writes: > Hi Rusty, > > After merging the modules tree, today's linux-next build (powerpc > ppc64_defconfig) failed like this: As this is in Andrew's tree, I've reverted it from my modules-next tree. Thanks, Rusty. -- To unsubscribe from this list: send the line "unsubscribe

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/pasemi/idle.c:88:1: error: macro "__define_initcall" passed 3 arguments, but takes just 2 arch/powerpc/platforms/pasemi/idle.c:88:1: error: data definition has

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

Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/pasemi/idle.c:88:1: error: macro __define_initcall passed 3 arguments, but takes just 2 arch/powerpc/platforms/pasemi/idle.c:88:1: error: data definition has no

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

Stephen Rothwell s...@canb.auug.org.au writes: Hi Rusty, After merging the modules tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: As this is in Andrew's tree, I've reverted it from my modules-next tree. Thanks, Rusty. -- To unsubscribe from this list: send the