[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190213142911.f4447df2b30cc8ced2a1bb82@linux-foundation.org>
Date: Wed, 13 Feb 2019 14:29:11 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jens Axboe <axboe@...nel.dk>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Nikolay Borisov <nborisov@...e.com>
Subject: Re: linux-next: build failure after merge of the akpm-current tree
On Wed, 13 Feb 2019 17:25:18 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> fs/io_uring.c: In function 'io_async_list_note':
> fs/io_uring.c:931:16: error: 'VM_MAX_READAHEAD' undeclared (first use in this function); did you mean 'VM_MAYREAD'?
> max_pages = VM_MAX_READAHEAD >> (PAGE_SHIFT - 10);
> ^~~~~~~~~~~~~~~~
> VM_MAYREAD
>
> Caused by commit
>
> 4c416502dae2 ("mm: Refactor readahead defines in mm.h")
>
> interacting with commit
>
> 6eff5fa16a2e ("io_uring: allow workqueue item to handle multiple buffered requests")
>
> from the block tree.
>
Thanks. I'll fix mm-refactor-readahead-defines-in-mmh.patch and shall
stage it after the block tree so everything lands nicely.
Powered by blists - more mailing lists