From: Keith Busch <kbusch@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@meta.com>,
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,
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>,
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
Subject: Re: [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf
Date: Mon, 9 Jan 2023 08:12:13 -0700 [thread overview]
Message-ID: <Y7wuzaXhypvExrNF@kbusch-mbp> (raw)
In-Reply-To: <1880281.1673256668@warthog.procyon.org.uk>
On Mon, Jan 09, 2023 at 09:31:08AM +0000, David Howells wrote:
> lore.kernel.org doesn't seem to have the patches.
>
> https://lore.kernel.org/lkml/20230105190741.2405013-1-kbusch@meta.com/
That's frustrating. Seems like an email setup problem on my end. I'll
split this series up and resend.
next prev parent reply other threads:[~2023-01-09 15:14 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 ` [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf Christoph Hellwig
2023-01-09 9:31 ` David Howells
2023-01-09 15:12 ` Keith Busch [this message]
[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=Y7wuzaXhypvExrNF@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=jarkko@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.