[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <27de542b-aa30-78e4-40ad-4a024e42e643@kernel.dk>
Date: Sun, 27 Oct 2019 21:25:04 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the block tree
On 10/27/19 8:59 PM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the block tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> fs/io_uring.c: In function '__io_sqe_files_unregister':
> fs/io_uring.c:3010:12: error: invalid storage class for function 'io_sqe_files_unregister'
> 3010 | static int io_sqe_files_unregister(struct io_ring_ctx *ctx)
> | ^~~~~~~~~~~~~~~~~~~~~~~
> fs/io_uring.c:3010:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
> 3010 | static int io_sqe_files_unregister(struct io_ring_ctx *ctx)
> | ^~~~~~
>
> Caused by commit
>
> ed9e02e4bad1 ("io_uring: support for larger fixed file sets")
>
> I have used the block tree from next-20191025 for today.
Ah shoot, forgot to update for-next, I did fix this silly error
yesterday. If you're up for it, pull for-next again in 2 min and I'll
have it updated. If not, I guess it'll be there in the next one. Usually
doesn't matter, only asking because syzbot keeps flagging the same issue
that is also fixed.
--
Jens Axboe
Powered by blists - more mailing lists