From: Jens Axboe <[email protected]>
To: YueHaibing <[email protected]>,
[email protected], [email protected]
Cc: [email protected], [email protected],
[email protected]
Subject: Re: [PATCH -next] io_uring: Add missing include <linux/highmem.h>
Date: Fri, 29 Nov 2019 18:53:17 -0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/29/19 5:50 PM, YueHaibing wrote:
> Fix build error:
>
> fs/io_uring.c:1628:21: error: implicit declaration of function 'kmap' [-Werror=implicit-function-declaration]
> fs/io_uring.c:1643:4: error: implicit declaration of function 'kunmap' [-Werror=implicit-function-declaration]
>
> Reported-by: Hulk Robot <[email protected]>
> Fixes: 311ae9e159d8 ("io_uring: fix dead-hung for non-iter fixed rw")
> Signed-off-by: YueHaibing <[email protected]>
> ---
> fs/io_uring.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index 2c2e8c2..745eb00 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
> @@ -69,6 +69,7 @@
> #include <linux/nospec.h>
> #include <linux/sizes.h>
> #include <linux/hugetlb.h>
> +#include <linux/highmem.h>
>
> #define CREATE_TRACE_POINTS
> #include <trace/events/io_uring.h>
Fix for this is already queued up, and now sent to Linus as well:
https://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=aa4c3967756c6c576a38a23ac511be211462a6b7
--
Jens Axboe
prev parent reply other threads:[~2019-11-30 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 1:50 [PATCH -next] io_uring: Add missing include <linux/highmem.h> YueHaibing
2019-11-30 2:53 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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