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

On Fri, May 03, 2019 at 10:21:05AM +1000, Stephen Rothwell wrote: > Hi David, > > After merging the btrfs-kdave tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > fs/btrfs/props.c: In function 'inherit_props': > fs/btrfs/props.c:389:4: warning: 'num_bytes' may be

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/btrfs/props.c: In function 'inherit_props': fs/btrfs/props.c:389:4: warning: 'num_bytes' may be used uninitialized in this function [-Wmaybe-uninitialized]

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

On Thu, Jan 24, 2019 at 09:53:38AM +1100, Stephen Rothwell wrote: > Hi David, > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/relocation.c: In function 'insert_dirty_subv': > fs/btrfs/relocation.c:2138:6: warning:

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/relocation.c: In function 'insert_dirty_subv': fs/btrfs/relocation.c:2138:6: warning: unused variable 'root_objectid' [-Wunused-variable] u64 root_objectid =

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

On Mon, Nov 26, 2018 at 11:06:29AM +1100, Stephen Rothwell wrote: > Introduced by commit > > cf8cddd38bab3 ("btrfs: don't abuse REQ_OP_* flags for btrfs_map_block") > > exposed by my new use of -Wimplicit-fallthrough > > I am not sure why this has only turned up now (as opposed to earlier >

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

On Mon, Nov 26, 2018 at 11:06:29AM +1100, Stephen Rothwell wrote: > Introduced by commit > > cf8cddd38bab3 ("btrfs: don't abuse REQ_OP_* flags for btrfs_map_block") > > exposed by my new use of -Wimplicit-fallthrough > > I am not sure why this has only turned up now (as opposed to earlier >

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: In file included from include/linux/string.h:6, from arch/powerpc/include/asm/paca.h:19, from arch/powerpc/include/asm/current.h:16,

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: In file included from include/linux/string.h:6, from arch/powerpc/include/asm/paca.h:19, from arch/powerpc/include/asm/current.h:16,

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

On 2017年12月22日 00:49, David Sterba wrote: > On Wed, Dec 20, 2017 at 08:12:11AM +0800, Qu Wenruo wrote: >> On 2017年12月20日 06:20, Stephen Rothwell wrote: >>> After merging the btrfs-kdave tree, today's linux-next build (powerpc >>> ppc64_defconfig) produced this warning: >>> >>> fs/btrfs/qgroup.c:

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

On 2017年12月22日 00:49, David Sterba wrote: > On Wed, Dec 20, 2017 at 08:12:11AM +0800, Qu Wenruo wrote: >> On 2017年12月20日 06:20, Stephen Rothwell wrote: >>> After merging the btrfs-kdave tree, today's linux-next build (powerpc >>> ppc64_defconfig) produced this warning: >>> >>> fs/btrfs/qgroup.c:

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

On Wed, Dec 20, 2017 at 08:12:11AM +0800, Qu Wenruo wrote: > On 2017年12月20日 06:20, Stephen Rothwell wrote: > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > fs/btrfs/qgroup.c: In function 'qgroup_reserve': > >

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

On Wed, Dec 20, 2017 at 08:12:11AM +0800, Qu Wenruo wrote: > On 2017年12月20日 06:20, Stephen Rothwell wrote: > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > fs/btrfs/qgroup.c: In function 'qgroup_reserve': > >

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

On 2017年12月20日 06:20, Stephen Rothwell wrote: > Hi David, > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/qgroup.c: In function 'qgroup_reserve': > fs/btrfs/qgroup.c:2432:1: warning: label 'retry' defined but not

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

On 2017年12月20日 06:20, Stephen Rothwell wrote: > Hi David, > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/qgroup.c: In function 'qgroup_reserve': > fs/btrfs/qgroup.c:2432:1: warning: label 'retry' defined but not

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/qgroup.c: In function 'qgroup_reserve': fs/btrfs/qgroup.c:2432:1: warning: label 'retry' defined but not used [-Wunused-label] retry: ^ Introduced by commit

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/qgroup.c: In function 'qgroup_reserve': fs/btrfs/qgroup.c:2432:1: warning: label 'retry' defined but not used [-Wunused-label] retry: ^ Introduced by commit

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

Hi David, On Thu, 18 May 2017 14:50:00 +0200 David Sterba wrote: > > On Thu, May 18, 2017 at 09:41:46AM +1000, Stephen Rothwell wrote: > > Hi David, > > > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > >

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

Hi David, On Thu, 18 May 2017 14:50:00 +0200 David Sterba wrote: > > On Thu, May 18, 2017 at 09:41:46AM +1000, Stephen Rothwell wrote: > > Hi David, > > > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > >

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

On Thu, May 18, 2017 at 09:41:46AM +1000, Stephen Rothwell wrote: > Hi David, > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/inode.c: In function 'btrfs_submit_direct': > fs/btrfs/inode.c:8467:14: warning: 'bio'

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

On Thu, May 18, 2017 at 09:41:46AM +1000, Stephen Rothwell wrote: > Hi David, > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/inode.c: In function 'btrfs_submit_direct': > fs/btrfs/inode.c:8467:14: warning: 'bio'

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/inode.c: In function 'btrfs_submit_direct': fs/btrfs/inode.c:8467:14: warning: 'bio' may be used uninitialized in this function [-Wmaybe-uninitialized] struct bio

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/inode.c: In function 'btrfs_submit_direct': fs/btrfs/inode.c:8467:14: warning: 'bio' may be used uninitialized in this function [-Wmaybe-uninitialized] struct bio

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

On Wed, Dec 07, 2016 at 09:38:19AM +1100, Stephen Rothwell wrote: > Hi David, > > On Mon, 28 Nov 2016 11:02:30 +1100 Stephen Rothwell > wrote: > > > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > >

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

On Wed, Dec 07, 2016 at 09:38:19AM +1100, Stephen Rothwell wrote: > Hi David, > > On Mon, 28 Nov 2016 11:02:30 +1100 Stephen Rothwell > wrote: > > > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > fs/btrfs/inode.c: In

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

Hi David, On Mon, 28 Nov 2016 11:02:30 +1100 Stephen Rothwell wrote: > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/inode.c: In function 'run_delalloc_range': > fs/btrfs/inode.c:1219:9:

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

Hi David, On Mon, 28 Nov 2016 11:02:30 +1100 Stephen Rothwell wrote: > > After merging the btrfs-kdave tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/btrfs/inode.c: In function 'run_delalloc_range': > fs/btrfs/inode.c:1219:9: warning: 'cur_end' may be

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/inode.c: In function 'run_delalloc_range': fs/btrfs/inode.c:1219:9: warning: 'cur_end' may be used uninitialized in this function [-Wmaybe-uninitialized] start =

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/btrfs/inode.c: In function 'run_delalloc_range': fs/btrfs/inode.c:1219:9: warning: 'cur_end' may be used uninitialized in this function [-Wmaybe-uninitialized] start =