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

Randy, On 2/24/21 13:45, Randy Dunlap wrote: > On 2/24/21 1:41 PM, Chaitanya Kulkarni wrote: >> On 2/24/21 02:43, Stephen Rothwell wrote: I'll setup doc generation using sphinx on my machine, is there a particular command line that you have used for these warnings ? >>> I just do a

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

On 2/24/21 1:41 PM, Chaitanya Kulkarni wrote: > On 2/24/21 02:43, Stephen Rothwell wrote: >>> I'll setup doc generation using sphinx on my machine, is there >>> a particular command line that you have used for these warnings ? >> I just do a "make htmldocs" > I did that, please have a look at the

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

On 2/24/21 02:43, Stephen Rothwell wrote: >> I'll setup doc generation using sphinx on my machine, is there >> a particular command line that you have used for these warnings ? > I just do a "make htmldocs" I did that, please have a look at the test log.

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

Hi Chaitanya, On Wed, 24 Feb 2021 05:38:06 + Chaitanya Kulkarni wrote: > > On 2/23/21 21:33, Stephen Rothwell wrote: > >> I've failed to understand this warning as rwbs is present in the doc header > >> and in the function parameter :- > > I presume it is the missing ':' after @rwbs in

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

On 2/23/21 21:33, Stephen Rothwell wrote: >>> 1f83bb4b4914 ("blktrace: add blk_fill_rwbs documentation comment") >>> >>> -- Cheers, Stephen Rothwell >> I've failed to understand this warning as rwbs is present in the doc header >> and in the function parameter :- > I presume it is the missing

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

On 2/23/21 21:33, Stephen Rothwell wrote: >> I've failed to understand this warning as rwbs is present in the doc header >> and in the function parameter :- > I presume it is the missing ':' after @rwbs in the comment. Thanks, I was looking at the wrong places all this time, will send a fix. I'll

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

Hi Chaitanya, On Wed, 24 Feb 2021 05:25:49 + Chaitanya Kulkarni wrote: > > On 2/23/21 18:31, Stephen Rothwell wrote: > > Hi all, > > > > After merging the block tree, today's linux-next build (htmldocs) > > produced this warning: > > > > kernel/trace/blktrace.c:1878: warning: Function

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

Stephen, On 2/23/21 18:31, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (htmldocs) > produced this warning: > > kernel/trace/blktrace.c:1878: warning: Function parameter or member 'rwbs' > not described in 'blk_fill_rwbs'` > > Introduced by commit

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

On 2/23/21 18:31, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (htmldocs) > produced this warning: > > kernel/trace/blktrace.c:1878: warning: Function parameter or member 'rwbs' > not described in 'blk_fill_rwbs'` > > Introduced by commit > >

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

Hi all, After merging the block tree, today's linux-next build (htmldocs) produced this warning: kernel/trace/blktrace.c:1878: warning: Function parameter or member 'rwbs' not described in 'blk_fill_rwbs'` Introduced by commit 1f83bb4b4914 ("blktrace: add blk_fill_rwbs documentation

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

On 12/22/20 4:47 PM, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > fs/io_uring.c: In function 'io_uring_get_file': > fs/io_uring.c:9408:6: warning: unused variable 'ret' [-Wunused-variable] > 9408

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

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/io_uring.c: In function 'io_uring_get_file': fs/io_uring.c:9408:6: warning: unused variable 'ret' [-Wunused-variable] 9408 | int ret; | ^~~ Introduced by commit

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

Hi all, On Tue, 15 Dec 2020 07:14:36 +1100 Stephen Rothwell wrote: > > On Thu, 3 Dec 2020 18:39:58 +1100 Stephen Rothwell > wrote: > > > > After merging the block tree, today's linux-next build (htmldocs) > > produced this warning: > > > > fs/block_dev.c:1838: warning: Function parameter or

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

Hi all, On Tue, 15 Dec 2020 07:13:40 +1100 Stephen Rothwell wrote: > > On Thu, 3 Dec 2020 18:37:40 +1100 Stephen Rothwell > wrote: > > > > After merging the block tree, today's linux-next build (htmldocs) > > produced this warning: > > > > fs/block_dev.c:1067: warning: Excess function

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

Hi all, On Thu, 3 Dec 2020 18:39:58 +1100 Stephen Rothwell wrote: > > After merging the block tree, today's linux-next build (htmldocs) > produced this warning: > > fs/block_dev.c:1838: warning: Function parameter or member 'dev' not > described in 'lookup_bdev' > > Introduced by commit > >

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

Hi all, On Thu, 3 Dec 2020 18:37:40 +1100 Stephen Rothwell wrote: > > After merging the block tree, today's linux-next build (htmldocs) > produced this warning: > > fs/block_dev.c:1067: warning: Excess function parameter 'whole' description > in 'bd_abort_claiming' > > Introduced by commit >

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

Hi all, After merging the block tree, today's linux-next build (htmldocs) produced this warning: kernel/trace/blktrace.c:1039: warning: Excess function parameter 'q' description in 'blk_add_trace_rq_remap' Introduced by commit a54895fa057c ("block: remove the request_queue to argument

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

Hi all, After merging the block tree, today's linux-next build (htmldocs) produced this warning: fs/block_dev.c:1838: warning: Function parameter or member 'dev' not described in 'lookup_bdev' Introduced by commit 4e7b5671c6a8 ("block: remove i_bdev") -- Cheers, Stephen Rothwell

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

Hi all, After merging the block tree, today's linux-next build (htmldocs) produced this warning: fs/block_dev.c:1067: warning: Excess function parameter 'whole' description in 'bd_abort_claiming' Introduced by commit 37c3fc9abb25 ("block: simplify the block device claiming interface") --

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

Hi all, After merging the block tree, today's linux-next build (htmldocs) produced this warning: block/genhd.c:439: warning: Function parameter or member 'probe' not described in '__register_blkdev' Introduced by commit 3da1a61e7046 ("block: add an optional probe callback to major_names")

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

On 10/22/20 5:48 PM, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (KCONFIG_NAME) > produced this warning: > > fs/io_uring.c: In function 'loop_rw_iter': > fs/io_uring.c:3141:21: warning: cast to pointer from integer of different > size

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

Hi all, After merging the block tree, today's linux-next build (KCONFIG_NAME) produced this warning: fs/io_uring.c: In function 'loop_rw_iter': fs/io_uring.c:3141:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 3141 |iovec.iov_base = (void __user *)

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

On 7/1/20 7:21 PM, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > drivers/md/dm.c: In function '__map_bio': > drivers/md/dm.c:1296:24: warning: unused variable 'md' [-Wunused-variable] > 1296 |

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

Hi all, After merging the block tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/md/dm.c: In function '__map_bio': drivers/md/dm.c:1296:24: warning: unused variable 'md' [-Wunused-variable] 1296 | struct mapped_device *md = io->md; |

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

Hi Jens, On Thu, 17 Oct 2019 18:56:39 -0600 Jens Axboe wrote: > > I'll fix these warnings up, guessing it's 32-bit? Thanks. Yeah 32 bit. -- Cheers, Stephen Rothwell pgpAAZTHyaXeP.pgp Description: OpenPGP digital signature

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

On 10/17/19 6:56 PM, Jens Axboe wrote: > On 10/17/19 6:51 PM, Stephen Rothwell wrote: >> Hi all, >> >> After merging the block tree, today's linux-next build (arm >> multi_v7_defconfig) produced this warning: >> >> fs/io_uring.c: In function 'io_accept': >> fs/io_uring.c:1729:9: warning: cast to

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

On 10/17/19 6:51 PM, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > fs/io_uring.c: In function 'io_accept': > fs/io_uring.c:1729:9: warning: cast to pointer from integer of different size >

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

Hi all, After merging the block tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: fs/io_uring.c: In function 'io_accept': fs/io_uring.c:1729:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 1729 | addr = (struct sockaddr __user *)

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

On 8/29/19 9:41 AM, Tejun Heo wrote: > On Thu, Aug 29, 2019 at 02:08:28PM +1000, Stephen Rothwell wrote: >> From: Stephen Rothwell >> Date: Thu, 29 Aug 2019 14:03:43 +1000 >> Subject: [PATCH] blkcg: blk-iocost: predeclare used structs >> >> Signed-off-by: Stephen Rothwell > > Acked-by: Tejun

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

On Thu, Aug 29, 2019 at 02:08:28PM +1000, Stephen Rothwell wrote: > From: Stephen Rothwell > Date: Thu, 29 Aug 2019 14:03:43 +1000 > Subject: [PATCH] blkcg: blk-iocost: predeclare used structs > > Signed-off-by: Stephen Rothwell Acked-by: Tejun Heo Thanks. > --- >

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

Hi all, On Thu, 29 Aug 2019 13:51:50 +1000 Stephen Rothwell wrote: > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > In file included from include/trace/events/iocost.h:8, > from : >

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

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/trace/events/iocost.h:8, from : include/trace/events/iocost.h:12:57: warning: 'struct ioc_now' declared inside parameter list will not be

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

On 2019/8/9 12:00, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/lightnvm/pblk-read.c: In function 'pblk_submit_read_gc': > drivers/lightnvm/pblk-read.c:421:18: warning: unused variable

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

On 8/8/19 9:00 PM, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/lightnvm/pblk-read.c: In function 'pblk_submit_read_gc': > drivers/lightnvm/pblk-read.c:421:18: warning: unused variable

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

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/lightnvm/pblk-read.c: In function 'pblk_submit_read_gc': drivers/lightnvm/pblk-read.c:421:18: warning: unused variable 'geo' [-Wunused-variable] struct nvm_geo *geo = >geo;

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

On 2019/4/18 22:01, Jaegeuk Kim wrote: > On 04/18, Chao Yu wrote: >> On 2019/4/17 22:03, Jaegeuk Kim wrote: >>> On 04/17, Chao Yu wrote: Hi Jaegeuk, On 2019/4/17 10:31, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64

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

On 04/18, Chao Yu wrote: > On 2019/4/17 22:03, Jaegeuk Kim wrote: > > On 04/17, Chao Yu wrote: > >> Hi Jaegeuk, > >> > >> On 2019/4/17 10:31, Stephen Rothwell wrote: > >>> Hi all, > >>> > >>> After merging the block tree, today's linux-next build (x86_64 > >>> allmodconfig) produced this warning:

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

On 2019/4/17 22:03, Jaegeuk Kim wrote: > On 04/17, Chao Yu wrote: >> Hi Jaegeuk, >> >> On 2019/4/17 10:31, Stephen Rothwell wrote: >>> Hi all, >>> >>> After merging the block tree, today's linux-next build (x86_64 >>> allmodconfig) produced this warning: >>> >>> fs/f2fs/node.c: In function

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

On 04/17, Chao Yu wrote: > Hi Jaegeuk, > > On 2019/4/17 10:31, Stephen Rothwell wrote: > > Hi all, > > > > After merging the block tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > > > fs/f2fs/node.c: In function 'f2fs_remove_inode_page': > >

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

Hi Jaegeuk, On 2019/4/17 10:31, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > fs/f2fs/node.c: In function 'f2fs_remove_inode_page': > fs/f2fs/node.c:1193:47: warning: format '%zu' expects argument

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

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/f2fs/node.c: In function 'f2fs_remove_inode_page': fs/f2fs/node.c:1193:47: warning: format '%zu' expects argument of type 'size_t', but argument 5 has type 'blkcnt_t' {aka 'long long

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

On 11/7/18 8:31 PM, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (sparc64 defconfig) > produced this warning: > > /home/sfr/next/next/drivers/block/sunvdc.c: In function 'init_queue': > /home/sfr/next/next/drivers/block/sunvdc.c:788:6: warning:

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

On 11/7/18 8:31 PM, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (sparc64 defconfig) > produced this warning: > > /home/sfr/next/next/drivers/block/sunvdc.c: In function 'init_queue': > /home/sfr/next/next/drivers/block/sunvdc.c:788:6: warning:

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

Hi Jens, After merging the block tree, today's linux-next build (sparc64 defconfig) produced this warning: /home/sfr/next/next/drivers/block/sunvdc.c: In function 'init_queue': /home/sfr/next/next/drivers/block/sunvdc.c:788:6: warning: unused variable 'ret' [-Wunused-variable] int ret;

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

Hi Jens, After merging the block tree, today's linux-next build (sparc64 defconfig) produced this warning: /home/sfr/next/next/drivers/block/sunvdc.c: In function 'init_queue': /home/sfr/next/next/drivers/block/sunvdc.c:788:6: warning: unused variable 'ret' [-Wunused-variable] int ret;

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

On 9/28/18 12:43 AM, Omar Sandoval wrote: > On Fri, Sep 28, 2018 at 11:11:24AM +1000, Stephen Rothwell wrote: >> Hi Jens, >> >> After merging the block tree, today's linux-next build (arm >> multi_v7_defconfig) produced this warning: >> >> block/kyber-iosched.c:84:22: warning: integer overflow in

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

On 9/28/18 12:43 AM, Omar Sandoval wrote: > On Fri, Sep 28, 2018 at 11:11:24AM +1000, Stephen Rothwell wrote: >> Hi Jens, >> >> After merging the block tree, today's linux-next build (arm >> multi_v7_defconfig) produced this warning: >> >> block/kyber-iosched.c:84:22: warning: integer overflow in

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

On Fri, Sep 28, 2018 at 11:11:24AM +1000, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > block/kyber-iosched.c:84:22: warning: integer overflow in expression of type > 'long int' results in

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

On Fri, Sep 28, 2018 at 11:11:24AM +1000, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > block/kyber-iosched.c:84:22: warning: integer overflow in expression of type > 'long int' results in

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

Hi Jens, After merging the block tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: block/kyber-iosched.c:84:22: warning: integer overflow in expression of type 'long int' results in '705032704' [-Woverflow] [KYBER_DISCARD] = 5 * NSEC_PER_SEC,

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

Hi Jens, After merging the block tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: block/kyber-iosched.c:84:22: warning: integer overflow in expression of type 'long int' results in '705032704' [-Woverflow] [KYBER_DISCARD] = 5 * NSEC_PER_SEC,

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

Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/md/md.c: In function 'mddev_put': drivers/md/md.c:543:1: warning: the frame size of 2080 bytes is larger than 2048 bytes [-Wframe-larger-than=] } ^ This is caused because

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

Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/md/md.c: In function 'mddev_put': drivers/md/md.c:543:1: warning: the frame size of 2080 bytes is larger than 2048 bytes [-Wframe-larger-than=] } ^ This is caused because

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

On 5/14/18 2:29 AM, Christoph Hellwig wrote: > On Mon, May 14, 2018 at 12:51:39PM +1000, Stephen Rothwell wrote: >> Hi all, >> >> After merging the block tree, today's linux-next build (x86_64 >> allmodconfig) produced this warning: > > The look entirely correct, but oddly enough my compiler did

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

On 5/14/18 2:29 AM, Christoph Hellwig wrote: > On Mon, May 14, 2018 at 12:51:39PM +1000, Stephen Rothwell wrote: >> Hi all, >> >> After merging the block tree, today's linux-next build (x86_64 >> allmodconfig) produced this warning: > > The look entirely correct, but oddly enough my compiler did

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

On Mon, May 14, 2018 at 12:51:39PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: The look entirely correct, but oddly enough my compiler did not bother to warn. Fix below: -- >From

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

On Mon, May 14, 2018 at 12:51:39PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the block tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: The look entirely correct, but oddly enough my compiler did not bother to warn. Fix below: -- >From

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

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/memstick/core/mspro_block.c: In function 'mspro_block_init_disk': drivers/memstick/core/mspro_block.c:1173:24: warning: unused variable 'host' [-Wunused-variable] struct

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

Hi all, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/memstick/core/mspro_block.c: In function 'mspro_block_init_disk': drivers/memstick/core/mspro_block.c:1173:24: warning: unused variable 'host' [-Wunused-variable] struct

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

On 2017.05.09 at 21:00 -0600, Jens Axboe wrote: > On 05/09/2017 08:20 PM, Markus Trippelsdorf wrote: > > On 2017.05.10 at 11:24 +1000, Stephen Rothwell wrote: > >> Hi Jens, > >> > >> After merging the block tree, today's linux-next build (arm > >> multi_v7_defconfig) produced this warning: > >> >

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

On 2017.05.09 at 21:00 -0600, Jens Axboe wrote: > On 05/09/2017 08:20 PM, Markus Trippelsdorf wrote: > > On 2017.05.10 at 11:24 +1000, Stephen Rothwell wrote: > >> Hi Jens, > >> > >> After merging the block tree, today's linux-next build (arm > >> multi_v7_defconfig) produced this warning: > >> >

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

Hi Markus, On Wed, 10 May 2017 04:20:54 +0200 Markus Trippelsdorf wrote: > > Yes, it was missing a (void) like "(void)strlcpy(...)". But Jens > unfortunately removed both warnings, so the following patch should now > be enough: > > diff --git a/block/elevator.c

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

Hi Markus, On Wed, 10 May 2017 04:20:54 +0200 Markus Trippelsdorf wrote: > > Yes, it was missing a (void) like "(void)strlcpy(...)". But Jens > unfortunately removed both warnings, so the following patch should now > be enough: > > diff --git a/block/elevator.c b/block/elevator.c > index

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

On 05/09/2017 08:20 PM, Markus Trippelsdorf wrote: > On 2017.05.10 at 11:24 +1000, Stephen Rothwell wrote: >> Hi Jens, >> >> After merging the block tree, today's linux-next build (arm >> multi_v7_defconfig) produced this warning: >> >> block/elevator.c: In function 'elv_iosched_store': >>

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

On 05/09/2017 08:20 PM, Markus Trippelsdorf wrote: > On 2017.05.10 at 11:24 +1000, Stephen Rothwell wrote: >> Hi Jens, >> >> After merging the block tree, today's linux-next build (arm >> multi_v7_defconfig) produced this warning: >> >> block/elevator.c: In function 'elv_iosched_store': >>

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

On 2017.05.10 at 11:24 +1000, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > block/elevator.c: In function 'elv_iosched_store': > block/elevator.c:1102:2: warning: ignoring return value of

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

On 2017.05.10 at 11:24 +1000, Stephen Rothwell wrote: > Hi Jens, > > After merging the block tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > block/elevator.c: In function 'elv_iosched_store': > block/elevator.c:1102:2: warning: ignoring return value of

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

Hi Jens, After merging the block tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: block/elevator.c: In function 'elv_iosched_store': block/elevator.c:1102:2: warning: ignoring return value of 'strstrip', declared with attribute warn_unused_result [-Wunused-result]

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

Hi Jens, After merging the block tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: block/elevator.c: In function 'elv_iosched_store': block/elevator.c:1102:2: warning: ignoring return value of 'strstrip', declared with attribute warn_unused_result [-Wunused-result]

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

On 2014-10-22 19:28, Stephen Rothwell wrote: Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: block/scsi_ioctl.c: In function 'sg_scsi_ioctl': block/scsi_ioctl.c:520:1: warning: label 'out' defined but not used [-Wunused-label]

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

Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: block/scsi_ioctl.c: In function 'sg_scsi_ioctl': block/scsi_ioctl.c:520:1: warning: label 'out' defined but not used [-Wunused-label] out: ^ Introduced by commit 374f8fdea4aa ("scsi:

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

Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: block/scsi_ioctl.c: In function 'sg_scsi_ioctl': block/scsi_ioctl.c:520:1: warning: label 'out' defined but not used [-Wunused-label] out: ^ Introduced by commit 374f8fdea4aa (scsi:

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

On 2014-10-22 19:28, Stephen Rothwell wrote: Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: block/scsi_ioctl.c: In function 'sg_scsi_ioctl': block/scsi_ioctl.c:520:1: warning: label 'out' defined but not used [-Wunused-label]

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

Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/kernel.h:13:0, from drivers/block/skd_main.c:19: drivers/block/skd_main.c: In function 'skd_cons_skmsg':

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

Hi Jens, After merging the block tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/kernel.h:13:0, from drivers/block/skd_main.c:19: drivers/block/skd_main.c: In function 'skd_cons_skmsg':