From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
linux-aio@kvack.org, linux-fsdevel@vger.kernel.org, hch@lst.de,
io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
davem@davemloft.net, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Paul Moore <paul@paul-moore.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-block@vger.kernel.org,
netdev@vger.kernel.org, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf
Date: Sun, 8 Jan 2023 18:12:41 +0100 [thread overview]
Message-ID: <20230108171241.GA20314@lst.de> (raw)
In-Reply-To: <20230105190741.2405013-1-kbusch@meta.com>
The entire series looks good to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next parent reply other threads:[~2023-01-08 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230105190741.2405013-1-kbusch@meta.com>
2023-01-08 17:12 ` Christoph Hellwig [this message]
2023-01-09 9:31 ` [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf David Howells
2023-01-09 15:12 ` Keith Busch
[not found] ` <20230105190741.2405013-3-kbusch@meta.com>
2023-01-09 3:49 ` [PATCHv2 02/12] io_uring: switch network send/recv to ITER_UBUF Jens Axboe
2023-01-09 3:51 ` [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf Jens Axboe
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=20230108171241.GA20314@lst.de \
--to=hch@lst.de \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=io-uring@vger.kernel.org \
--cc=jarkko@kernel.org \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=keyrings@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-aio@kvack.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.