From: Pavel Begunkov <asml.silence@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH -next] fs: io_uring: build when CONFIG_NET is disabled
Date: Wed, 10 Feb 2021 17:38:53 +0000 [thread overview]
Message-ID: <f9dbd75d-cbce-292a-b9e4-7cf8fb6f4cd7@gmail.com> (raw)
In-Reply-To: <20210210173740.22328-1-rdunlap@infradead.org>
On 10/02/2021 17:37, Randy Dunlap wrote:
> Fix build errors when CONFIG_NET is not enabled.
Thanks, but already fixed up.
>
> Fixes: b268c951abf8 ("io_uring: don't propagate io_comp_state")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Pavel Begunkov <asml.silence@gmail.com>
> Cc: Jens Axboe <axboe@kernel.dk>
> Cc: linux-fsdevel@vger.kernel.org
> ---
> fs/io_uring.c | 18 ++++++------------
> 1 file changed, 6 insertions(+), 12 deletions(-)
>
> --- linux-next-20210210.orig/fs/io_uring.c
> +++ linux-next-20210210/fs/io_uring.c
> @@ -5145,14 +5145,12 @@ static int io_sendmsg_prep(struct io_kio
> return -EOPNOTSUPP;
> }
>
> -static int io_sendmsg(struct io_kiocb *req, unsigned int issue_flags,
> - struct io_comp_state *cs)
> +static int io_sendmsg(struct io_kiocb *req, unsigned int issue_flags)
> {
> return -EOPNOTSUPP;
> }
>
> -static int io_send(struct io_kiocb *req, unsigned int issue_flags,
> - struct io_comp_state *cs)
> +static int io_send(struct io_kiocb *req, unsigned int issue_flags)
> {
> return -EOPNOTSUPP;
> }
> @@ -5163,14 +5161,12 @@ static int io_recvmsg_prep(struct io_kio
> return -EOPNOTSUPP;
> }
>
> -static int io_recvmsg(struct io_kiocb *req, unsigned int issue_flags,
> - struct io_comp_state *cs)
> +static int io_recvmsg(struct io_kiocb *req, unsigned int issue_flags)
> {
> return -EOPNOTSUPP;
> }
>
> -static int io_recv(struct io_kiocb *req, unsigned int issue_flags,
> - struct io_comp_state *cs)
> +static int io_recv(struct io_kiocb *req, unsigned int issue_flags)
> {
> return -EOPNOTSUPP;
> }
> @@ -5180,8 +5176,7 @@ static int io_accept_prep(struct io_kioc
> return -EOPNOTSUPP;
> }
>
> -static int io_accept(struct io_kiocb *req, unsigned int issue_flags,
> - struct io_comp_state *cs)
> +static int io_accept(struct io_kiocb *req, unsigned int issue_flags)
> {
> return -EOPNOTSUPP;
> }
> @@ -5191,8 +5186,7 @@ static int io_connect_prep(struct io_kio
> return -EOPNOTSUPP;
> }
>
> -static int io_connect(struct io_kiocb *req, unsigned int issue_flags,
> - struct io_comp_state *cs)
> +static int io_connect(struct io_kiocb *req, unsigned int issue_flags)
> {
> return -EOPNOTSUPP;
> }
>
--
Pavel Begunkov
prev parent reply other threads:[~2021-02-10 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 17:37 [PATCH -next] fs: io_uring: build when CONFIG_NET is disabled Randy Dunlap
2021-02-10 17:38 ` Pavel Begunkov [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=f9dbd75d-cbce-292a-b9e4-7cf8fb6f4cd7@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).