Re: linux-next: build warning after merge of the tip tree

On Mon, 14 Dec 2020 at 06:48, Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > In file included from include/linux/kernel.h:14, > from include/linux/list.h:9, > from

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: In file included from include/linux/kernel.h:14, from include/linux/list.h:9, from include/linux/wait.h:7, from

Re: linux-next: build warning after merge of the tip tree

Hi Balbir, On Tue, 17 Nov 2020 16:21:31 +1100 Balbir Singh wrote: > > I am testing a fix by pointing the ref to a label, will send it out > (hopefully soon), seems to work at my end. Fixes the warning here as well, thanks. -- Cheers, Stephen Rothwell pgpDlpETEsg3r.pgp Description: OpenPGP

Re: linux-next: build warning after merge of the tip tree

On 11/16/20 9:23 AM, Balbir Singh wrote: > > > On 10/28/20 2:23 PM, Stephen Rothwell wrote: >> Hi all, >> >> After merging the tip tree, today's linux-next build (htmldocs) produced >> this warning: >> >> Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined >> label:

Re: linux-next: build warning after merge of the tip tree

On 10/28/20 2:23 PM, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (htmldocs) produced > this warning: > > Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: > documentation/userspace-api/spec_ctrl.rst (if the link has

Re: linux-next: build warning after merge of the tip tree

Hi all, On Wed, 28 Oct 2020 14:23:00 +1100 Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (htmldocs) produced > this warning: > > Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: >

Re: linux-next: build warning after merge of the tip tree

Hi all, On Thu, 5 Nov 2020 18:06:00 +1100 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (htmldocs) produced > this warning: > > Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: > documentation/userspace-api/spec_ctrl.rst (if the

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (htmldocs) produced this warning: Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: documentation/userspace-api/spec_ctrl.rst (if the link has no caption the label must precede a section header)

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (htmldocs) produced this warning: Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: documentation/userspace-api/spec_ctrl.rst (if the link has no caption the label must precede a section header)

Re: linux-next: build warning after merge of the tip tree

On Thu, Oct 15, 2020 at 09:25:26AM +1100, Stephen Rothwell wrote: > Hi Kees, > > On Sun, 4 Oct 2020 19:44:52 -0700 Kees Cook wrote: > > > > On Sun, Oct 04, 2020 at 09:00:18PM +1100, Stephen Rothwell wrote: > > > Hi Kees, > > > > > > On Sun, 4 Oct 2020 01:27:01 -0700 Kees Cook > > > wrote: >

Re: linux-next: build warning after merge of the tip tree

Hi Kees, On Wed, 14 Oct 2020 16:10:05 -0700 Kees Cook wrote: > > I've pinged the thread of the patch (from Oct 4th) that fixes this. > Hopefully that or this email will float to the top for an x86 > maintainer. :) If it doesn't get picked up soon, I can try sending this > direct to Linus,

Re: linux-next: build warning after merge of the tip tree

Hi Kees, On Sun, 4 Oct 2020 19:44:52 -0700 Kees Cook wrote: > > On Sun, Oct 04, 2020 at 09:00:18PM +1100, Stephen Rothwell wrote: > > Hi Kees, > > > > On Sun, 4 Oct 2020 01:27:01 -0700 Kees Cook wrote: > > > > > > I assume CONFIG_CONSTRUCTORS is enabled for your build (it should be for > >

Re: linux-next: build warning after merge of the tip tree

On Thu, Oct 08, 2020 at 03:28:32PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > WARNING: modpost: EXPORT symbol "copy_mc_fragile" [vmlinux] version > generation failed, symbol will not be

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: modpost: EXPORT symbol "copy_mc_fragile" [vmlinux] version generation failed, symbol will not be versioned. Probably introduced by commit ec6347bb4339 ("x86, powerpc: Rename

Re: linux-next: build warning after merge of the tip tree

On Sun, Oct 04, 2020 at 09:00:18PM +1100, Stephen Rothwell wrote: > Hi Kees, > > On Sun, 4 Oct 2020 01:27:01 -0700 Kees Cook wrote: > > > > I assume CONFIG_CONSTRUCTORS is enabled for your build (it should be for > > yes, indeed. > > > allmodconfig). Does this patch fix it? (I'm kind of

Re: linux-next: build warning after merge of the tip tree

Hi Kees, On Sun, 4 Oct 2020 01:27:01 -0700 Kees Cook wrote: > > I assume CONFIG_CONSTRUCTORS is enabled for your build (it should be for yes, indeed. > allmodconfig). Does this patch fix it? (I'm kind of blindly guessing > based on my understanding of where this could be coming from...) > >

Re: linux-next: build warning after merge of the tip tree

On Sun, Oct 04, 2020 at 10:24:37AM +1100, Stephen Rothwell wrote: > Hi Kees, > > On Sat, 3 Oct 2020 14:54:46 -0700 Kees Cook wrote: > > > > On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > > > Hi all, > > > > > > After merging the tip tree, today's linux-next build (x86_64

Re: linux-next: build warning after merge of the tip tree

On Sun, Oct 04, 2020 at 10:24:37AM +1100, Stephen Rothwell wrote: > On Sat, 3 Oct 2020 14:54:46 -0700 Kees Cook wrote: > > On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > > > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > > produced this

Re: linux-next: build warning after merge of the tip tree

Hi Kees, On Sat, 3 Oct 2020 14:54:46 -0700 Kees Cook wrote: > > On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > produced this warning: > > > > x86_64-linux-gnu-ld: warning:

Re: linux-next: build warning after merge of the tip tree

On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from > `kernel/trace/trace_selftest_dynamic.o'

Re: linux-next: build warning after merge of the tip tree

On Thu, Oct 01, 2020 at 09:02:57PM +1000, Stephen Rothwell wrote: > Hi all, > > On Tue, 15 Sep 2020 08:35:53 +1000 Stephen Rothwell > wrote: > > > > Hi Kees, > > > > On Mon, 14 Sep 2020 13:11:37 -0700 Kees Cook wrote: > > > > > > On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell

Re: linux-next: build warning after merge of the tip tree

Hi all, On Tue, 15 Sep 2020 08:35:53 +1000 Stephen Rothwell wrote: > > Hi Kees, > > On Mon, 14 Sep 2020 13:11:37 -0700 Kees Cook wrote: > > > > On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig)

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc and powerpc64 allnoconfig) produced this warning: WARNING: unmet direct dependencies detected for PCI_MSI_ARCH_FALLBACKS Depends on [n]: PCI [=n] Selected by [y]: - PPC [=y] Introduced by commit 077ee78e3928

Re: linux-next: build warning after merge of the tip tree

Hi Kees, On Mon, 14 Sep 2020 13:11:37 -0700 Kees Cook wrote: > > On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > produced this warning: > > > > x86_64-linux-gnu-ld: warning: orphan section

Re: linux-next: build warning after merge of the tip tree

On Mon, Sep 14, 2020 at 01:22:49PM +1000, Stephen Rothwell wrote: > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from > `kernel/trace/trace_selftest_dynamic.o' being placed in

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_selftest_dynamic.o' being placed in section `.ctors.65435' x86_64-linux-gnu-ld: warning: orphan section

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: arch/x86/kernel/traps.c: In function 'exc_double_fault': arch/x86/kernel/traps.c:332:16: warning: unused variable 'address' [-Wunused-variable] 332 | unsigned long address = read_cr2();

Re: linux-next: build warning after merge of the tip tree

Ronnie mentioned that he will take a look ... On Tue, May 19, 2020 at 1:57 AM Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > fs/cifs/smb2inode.c: In function 'smb2_compound_op': >

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/cifs/smb2inode.c: In function 'smb2_compound_op': fs/cifs/smb2inode.c:424:1: warning: the frame size of 2736 bytes is larger than 2048 bytes [-Wframe-larger-than=] 424 | } | ^ I

Re: linux-next: build warning after merge of the tip tree

Hi Josh, On Thu, 25 Jul 2019 23:49:09 -0500 Josh Poimboeuf wrote: > > This will be fixed by: > > > https://lkml.kernel.org/r/51a4155c5bc2ca847a9cbe85c1c11918bb193141.1564086017.git.jpoim...@redhat.com Thanks -- Cheers, Stephen Rothwell pgpIcuqnFnGu_.pgp Description: OpenPGP digital

Re: linux-next: build warning after merge of the tip tree

On Fri, Jul 26, 2019 at 01:05:49PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool: > .altinstr_replacement+0x1c: redundant

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool: .altinstr_replacement+0x1c: redundant UACCESS disable Presuambly introduced/uncovered by commit 882a0db9d143 ("objtool:

Re: linux-next: build warning after merge of the tip tree

Hi all, On Tue, 6 Nov 2018 11:46:12 +1100 Stephen Rothwell wrote: > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > warning: include/asm-generic/atomic-instrumented.h is out-of-date. > warning: include/asm-generic/atomic-long.h is

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: warning: include/asm-generic/atomic-instrumented.h is out-of-date. warning: include/asm-generic/atomic-long.h is out-of-date. warning: include/linux/atomic-fallback.h is out-of-date.

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: warning: include/asm-generic/atomic-instrumented.h is out-of-date. warning: include/asm-generic/atomic-long.h is out-of-date. warning: include/linux/atomic-fallback.h is out-of-date.

Re: linux-next: build warning after merge of the tip tree

On Tue, 11 Sep 2018, Stephen Rothwell wrote: > After merging the tip tree, today's linux-next build (x86_64 allnoconfig) > produced this warning: > > arch/x86/kernel/cpu/common.c: In function 'syscall_init': > arch/x86/kernel/cpu/common.c:1534:6: warning: unused variable 'cpu' >

Re: linux-next: build warning after merge of the tip tree

On Tue, 11 Sep 2018, Stephen Rothwell wrote: > After merging the tip tree, today's linux-next build (x86_64 allnoconfig) > produced this warning: > > arch/x86/kernel/cpu/common.c: In function 'syscall_init': > arch/x86/kernel/cpu/common.c:1534:6: warning: unused variable 'cpu' >

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: arch/x86/kernel/cpu/common.c: In function 'syscall_init': arch/x86/kernel/cpu/common.c:1534:6: warning: unused variable 'cpu' [-Wunused-variable] int cpu = smp_processor_id(); ^~~

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: arch/x86/kernel/cpu/common.c: In function 'syscall_init': arch/x86/kernel/cpu/common.c:1534:6: warning: unused variable 'cpu' [-Wunused-variable] int cpu = smp_processor_id(); ^~~

Re: linux-next: build warning after merge of the tip tree

Hi Christoph, On Fri, 23 Mar 2018 09:31:34 +0100 Christoph Hellwig wrote: > > True. I'll send a fixup. Thanks. -- Cheers, Stephen Rothwell pgpatT5TbuEkF.pgp Description: OpenPGP digital signature

Re: linux-next: build warning after merge of the tip tree

Hi Christoph, On Fri, 23 Mar 2018 09:31:34 +0100 Christoph Hellwig wrote: > > True. I'll send a fixup. Thanks. -- Cheers, Stephen Rothwell pgpatT5TbuEkF.pgp Description: OpenPGP digital signature

Re: linux-next: build warning after merge of the tip tree

On Fri, Mar 23, 2018 at 01:28:53PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/swiotlb.c:748:13: warning: 'swiotlb_free_buffer' defined but not used > [-Wunused-function] > static

Re: linux-next: build warning after merge of the tip tree

On Fri, Mar 23, 2018 at 01:28:53PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/swiotlb.c:748:13: warning: 'swiotlb_free_buffer' defined but not used > [-Wunused-function] > static

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/swiotlb.c:748:13: warning: 'swiotlb_free_buffer' defined but not used [-Wunused-function] static bool swiotlb_free_buffer(struct device *dev, size_t size,

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/swiotlb.c:748:13: warning: 'swiotlb_free_buffer' defined but not used [-Wunused-function] static bool swiotlb_free_buffer(struct device *dev, size_t size,

Re: linux-next: build warning after merge of the tip tree

On Fri, 16 Mar 2018, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) > produced this warning: > > kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used > [-Wunused-function] > static bool

Re: linux-next: build warning after merge of the tip tree

On Fri, 16 Mar 2018, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) > produced this warning: > > kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used > [-Wunused-function] > static bool

Re: linux-next: build warning after merge of the tip tree

Hi Stephen, At 03/16/2018 01:52 PM, Dou Liyang wrote: Hi Stephen, At 03/16/2018 01:37 PM, Stephen Rothwell wrote: Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not

Re: linux-next: build warning after merge of the tip tree

Hi Stephen, At 03/16/2018 01:52 PM, Dou Liyang wrote: Hi Stephen, At 03/16/2018 01:37 PM, Stephen Rothwell wrote: Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not

Re: linux-next: build warning after merge of the tip tree

Hi Stephen, At 03/16/2018 01:37 PM, Stephen Rothwell wrote: Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool

Re: linux-next: build warning after merge of the tip tree

Hi Stephen, At 03/16/2018 01:37 PM, Stephen Rothwell wrote: Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool cpuhp_is_ap_state(enum cpuhp_state state) ^

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig) produced this warning: kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function] static bool cpuhp_is_ap_state(enum cpuhp_state state) ^

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: arch/x86/kernel/cpu/bugs.c:79:12: warning: 'spectre_v2_enabled' defined but not used [-Wunused-variable] static int spectre_v2_enabled = SPECTRE_V2_NONE; ^ Introduced by commit

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: arch/x86/kernel/cpu/bugs.c:79:12: warning: 'spectre_v2_enabled' defined but not used [-Wunused-variable] static int spectre_v2_enabled = SPECTRE_V2_NONE; ^ Introduced by commit

Re: linux-next: build warning after merge of the tip tree

On 09/26/2017 11:42 PM, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allnoconfig) > produced this warning: > > kernel/printk/printk.c:1983:12: warning: 'printk_time' defined but not used > [-Wunused-variable] > static int printk_time; >

Re: linux-next: build warning after merge of the tip tree

On 09/26/2017 11:42 PM, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allnoconfig) > produced this warning: > > kernel/printk/printk.c:1983:12: warning: 'printk_time' defined but not used > [-Wunused-variable] > static int printk_time; >

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: kernel/printk/printk.c:1983:12: warning: 'printk_time' defined but not used [-Wunused-variable] static int printk_time; ^ Introduced by commit 310b454a8653 ("printk: Add

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: kernel/printk/printk.c:1983:12: warning: 'printk_time' defined but not used [-Wunused-variable] static int printk_time; ^ Introduced by commit 310b454a8653 ("printk: Add

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: kernel/sched/fair.c:2657:9: warning: 'struct sched_domain' declared inside parameter list int prev_cpu, int sync) ^ /home/sfr/next/next/kernel/sched/fair.c:2657:9: warning:

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: kernel/sched/fair.c:2657:9: warning: 'struct sched_domain' declared inside parameter list int prev_cpu, int sync) ^ /home/sfr/next/next/kernel/sched/fair.c:2657:9: warning:

Re: linux-next: build warning after merge of the tip tree

Hi Michael, On Fri, 23 Jun 2017 14:10:25 +1000 Michael Ellerman wrote: > > Fixed in my next today by: > > d4cfb11387ee ("powerpc: Convert VDSO update function to use new > update_vsyscall interface") > > But you must have pulled before I pushed that, so the warning will

Re: linux-next: build warning after merge of the tip tree

Hi Michael, On Fri, 23 Jun 2017 14:10:25 +1000 Michael Ellerman wrote: > > Fixed in my next today by: > > d4cfb11387ee ("powerpc: Convert VDSO update function to use new > update_vsyscall interface") > > But you must have pulled before I pushed that, so the warning will go > away tomorrow.

Re: linux-next: build warning after merge of the tip tree

Stephen Rothwell writes: > Hi all, > > [Forgot to cc John] > > On Fri, 23 Jun 2017 13:58:34 +1000 Stephen Rothwell > wrote: >> >> Hi all, >> >> After merging the tip tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this

Re: linux-next: build warning after merge of the tip tree

Stephen Rothwell writes: > Hi all, > > [Forgot to cc John] > > On Fri, 23 Jun 2017 13:58:34 +1000 Stephen Rothwell > wrote: >> >> Hi all, >> >> After merging the tip tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> kernel/time/timekeeping.c:519:2:

Re: linux-next: build warning after merge of the tip tree

Hi all, [Forgot to cc John] On Fri, 23 Jun 2017 13:58:34 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > kernel/time/timekeeping.c:519:2: warning: #warning Please

Re: linux-next: build warning after merge of the tip tree

Hi all, [Forgot to cc John] On Fri, 23 Jun 2017 13:58:34 +1000 Stephen Rothwell wrote: > > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > kernel/time/timekeeping.c:519:2: warning: #warning Please contact your >

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: kernel/time/timekeeping.c:519:2: warning: #warning Please contact your maintainers, as GENERIC_TIME_VSYSCALL_OLD compatibity will disappear soon. [-Wcpp] #warning Please contact your

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: kernel/time/timekeeping.c:519:2: warning: #warning Please contact your maintainers, as GENERIC_TIME_VSYSCALL_OLD compatibity will disappear soon. [-Wcpp] #warning Please contact your

Re: linux-next: build warning after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > fs/ubifs/dir.c: In function 'ubifs_readdir': > fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in >

Re: linux-next: build warning after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > fs/ubifs/dir.c: In function 'ubifs_readdir': > fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in > this function

Re: linux-next: build warning after merge of the tip tree

Hi Richard, On Wed, 14 Dec 2016 09:05:10 +0100 Richard Weinberger wrote: > > The commit comes via my UBIFS tree. But I never saw this warning, I'm testing > with both gcc-4.8 and gcc-6.1. > Let me investigate into that. > > Does today's tip change some compiler flags? Linus'

Re: linux-next: build warning after merge of the tip tree

Hi Richard, On Wed, 14 Dec 2016 09:05:10 +0100 Richard Weinberger wrote: > > The commit comes via my UBIFS tree. But I never saw this warning, I'm testing > with both gcc-4.8 and gcc-6.1. > Let me investigate into that. > > Does today's tip change some compiler flags? Linus' tree commit

Re: linux-next: build warning after merge of the tip tree

Stephen, Ingo, CC'ing David. On 14.12.2016 08:24, Ingo Molnar wrote: > > * Stephen Rothwell wrote: > >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> produced this warning: >> >> fs/ubifs/dir.c: In function 'ubifs_readdir':

Re: linux-next: build warning after merge of the tip tree

Stephen, Ingo, CC'ing David. On 14.12.2016 08:24, Ingo Molnar wrote: > > * Stephen Rothwell wrote: > >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> produced this warning: >> >> fs/ubifs/dir.c: In function 'ubifs_readdir': >>

Re: linux-next: build warning after merge of the tip tree

Hi Ingo, On Wed, 14 Dec 2016 08:24:11 +0100 Ingo Molnar wrote: > > FYI, f4f61d2cc6d8 is not in the -tip tree, so it cannot possibly have > introduced > this warning. Yeah, I know, but the warning only seemed to happen after merging the tip tree. I would have expected it to

Re: linux-next: build warning after merge of the tip tree

Hi Ingo, On Wed, 14 Dec 2016 08:24:11 +0100 Ingo Molnar wrote: > > FYI, f4f61d2cc6d8 is not in the -tip tree, so it cannot possibly have > introduced > this warning. Yeah, I know, but the warning only seemed to happen after merging the tip tree. I would have expected it to appear much

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/ubifs/dir.c: In function 'ubifs_readdir': fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in this function [-Wmaybe-uninitialized] fstr.len = fstr_real_len;

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/ubifs/dir.c: In function 'ubifs_readdir': fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in this function [-Wmaybe-uninitialized] fstr.len = fstr_real_len;

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 05:42:09PM +0100, Mark Brown wrote: > On Mon, Jul 25, 2016 at 10:53:37AM -0400, Rich Felker wrote: > > On Mon, Jul 25, 2016 at 03:11:48PM +0200, Daniel Lezcano wrote: > > > > I don't know the goal of adding those patches in linux-next via your > > > tree, may be you

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 05:42:09PM +0100, Mark Brown wrote: > On Mon, Jul 25, 2016 at 10:53:37AM -0400, Rich Felker wrote: > > On Mon, Jul 25, 2016 at 03:11:48PM +0200, Daniel Lezcano wrote: > > > > I don't know the goal of adding those patches in linux-next via your > > > tree, may be you

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 10:53:37AM -0400, Rich Felker wrote: > On Mon, Jul 25, 2016 at 03:11:48PM +0200, Daniel Lezcano wrote: > > I don't know the goal of adding those patches in linux-next via your > > tree, may be you misunderstood how linux-next works and you should > > remove them. But if

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 10:53:37AM -0400, Rich Felker wrote: > On Mon, Jul 25, 2016 at 03:11:48PM +0200, Daniel Lezcano wrote: > > I don't know the goal of adding those patches in linux-next via your > > tree, may be you misunderstood how linux-next works and you should > > remove them. But if

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 03:11:48PM +0200, Daniel Lezcano wrote: > On 07/25/2016 09:16 AM, Thomas Gleixner wrote: > > On Sun, 24 Jul 2016, Stephen Rothwell wrote: > >> Hi all, > >> > >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > >> produced this warning: > >> > >>

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 03:11:48PM +0200, Daniel Lezcano wrote: > On 07/25/2016 09:16 AM, Thomas Gleixner wrote: > > On Sun, 24 Jul 2016, Stephen Rothwell wrote: > >> Hi all, > >> > >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > >> produced this warning: > >> > >>

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 09:16:48AM +0200, Thomas Gleixner wrote: > On Sun, 24 Jul 2016, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > produced this warning: > > > > In file included from

Re: linux-next: build warning after merge of the tip tree

On Mon, Jul 25, 2016 at 09:16:48AM +0200, Thomas Gleixner wrote: > On Sun, 24 Jul 2016, Stephen Rothwell wrote: > > Hi all, > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > produced this warning: > > > > In file included from

Re: linux-next: build warning after merge of the tip tree

On 07/25/2016 09:16 AM, Thomas Gleixner wrote: > On Sun, 24 Jul 2016, Stephen Rothwell wrote: >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> produced this warning: >> >> In file included from include/linux/clocksource.h:18:0, >> from

Re: linux-next: build warning after merge of the tip tree

On 07/25/2016 09:16 AM, Thomas Gleixner wrote: > On Sun, 24 Jul 2016, Stephen Rothwell wrote: >> Hi all, >> >> After merging the tip tree, today's linux-next build (x86_64 allmodconfig) >> produced this warning: >> >> In file included from include/linux/clocksource.h:18:0, >> from

Re: linux-next: build warning after merge of the tip tree

On Sun, 24 Jul 2016, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > In file included from include/linux/clocksource.h:18:0, > from include/linux/clockchips.h:13, >

Re: linux-next: build warning after merge of the tip tree

On Sun, 24 Jul 2016, Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > In file included from include/linux/clocksource.h:18:0, > from include/linux/clockchips.h:13, >

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/clocksource.h:18:0, from include/linux/clockchips.h:13, from drivers/clocksource/jcore-pit.c:14:

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/clocksource.h:18:0, from include/linux/clockchips.h:13, from drivers/clocksource/jcore-pit.c:14:

Re: linux-next: build warning after merge of the tip tree

Hi Ingo, On Thu, 7 Apr 2016 10:48:33 +0200 Ingo Molnar wrote: > > Indeed - and this only triggers on HAVE_GENERIC_RCU_GUP. > > I've amended the commit. Thanks. -- Cheers, Stephen Rothwell

Re: linux-next: build warning after merge of the tip tree

Hi Ingo, On Thu, 7 Apr 2016 10:48:33 +0200 Ingo Molnar wrote: > > Indeed - and this only triggers on HAVE_GENERIC_RCU_GUP. > > I've amended the commit. Thanks. -- Cheers, Stephen Rothwell

Re: linux-next: build warning after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc44x_defconfig) > produced this warning: > > mm/gup.c: In function 'get_user_pages_fast': > mm/gup.c:1510:20: warning: unused variable 'mm' [-Wunused-variable] >

Re: linux-next: build warning after merge of the tip tree

* Stephen Rothwell wrote: > Hi all, > > After merging the tip tree, today's linux-next build (powerpc > ppc44x_defconfig) > produced this warning: > > mm/gup.c: In function 'get_user_pages_fast': > mm/gup.c:1510:20: warning: unused variable 'mm' [-Wunused-variable] > struct mm_struct *mm =

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc44x_defconfig) produced this warning: mm/gup.c: In function 'get_user_pages_fast': mm/gup.c:1510:20: warning: unused variable 'mm' [-Wunused-variable] struct mm_struct *mm = current->mm; ^ Introduced

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (powerpc ppc44x_defconfig) produced this warning: mm/gup.c: In function 'get_user_pages_fast': mm/gup.c:1510:20: warning: unused variable 'mm' [-Wunused-variable] struct mm_struct *mm = current->mm; ^ Introduced

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allmodconfig) produced this warning: sound/drivers/pcsp/pcsp.c: In function 'snd_pcsp_create': sound/drivers/pcsp/pcsp.c:51:5: warning: format '%li' expects argument of type 'long int', but argument 2 has type 'unsigned int'

  1   2   >