From: Jens Axboe <axboe@kernel•dk>
To: Randy Dunlap <rdunlap@infradead•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Al Viro <viro@ZenIV•linux.org.uk>
Subject: Re: linux-next: Tree for Jun 18 (fs/io_uring)
Date: Thu, 18 Jun 2020 08:42:00 -0600 [thread overview]
Message-ID: <52b64a82-34c2-268f-7aa3-4cb4f7a14e23@kernel.dk> (raw)
In-Reply-To: <25b48bfa-07ef-c6c8-c4c9-61c213e22f66@infradead.org>
On 6/17/20 11:38 PM, Randy Dunlap wrote:
> On 6/17/20 9:15 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: there will be no linux-next release tomorrow.
>>
>> Changes since 20200617:
>>
>
> when CONFIG_BLOCK is not set/enabled:
>
> ../fs/io_uring.c: In function 'io_async_task_func':
> ../fs/io_uring.c:4559:7: error: implicit declaration of function 'io_sq_thread_acquire_mm'; did you mean 'atomic_read_acquire'? [-Werror=implicit-function-declaration]
> if (io_sq_thread_acquire_mm(ctx, req)) {
> ^~~~~~~~~~~~~~~~~~~~~~~
> atomic_read_acquire
> ../fs/io_uring.c: In function 'io_sq_thread':
> ../fs/io_uring.c:6268:4: error: implicit declaration of function 'io_sq_thread_drop_mm'; did you mean 'io_sq_thread'? [-Werror=implicit-function-declaration]
> io_sq_thread_drop_mm(ctx);
> ^~~~~~~~~~~~~~~~~~~~
> io_sq_thread
Fixed it up, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-06-18 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 4:15 linux-next: Tree for Jun 18 Stephen Rothwell
2020-06-18 5:38 ` linux-next: Tree for Jun 18 (fs/io_uring) Randy Dunlap
2020-06-18 14:42 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52b64a82-34c2-268f-7aa3-4cb4f7a14e23@kernel.dk \
--to=axboe@kernel$(echo .)dk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox