From: Keith Busch <kbusch@kernel.org>
To: Keith Busch <kbusch@meta.com>
Cc: ming.lei@redhat.com, asml.silence@gmail.com, axboe@kernel.dk,
linux-block@vger.kernel.org, io-uring@vger.kernel.org,
bernd@bsbernd.com, csander@purestorage.com,
linux-nvme@lists.infradead.org
Subject: Re: [PATCHv6 0/6] ublk zero copy support
Date: Wed, 26 Feb 2025 11:17:30 -0700 [thread overview]
Message-ID: <Z79auss5rprO8Dwp@kbusch-mbp> (raw)
In-Reply-To: <20250226181002.2574148-1-kbusch@meta.com>
I duplicated the format-patch command into the same directory, so I
completely screwed up this patch thread. Please disregard this one, and
we'll start a new one. Sorry for the noise.
prev parent reply other threads:[~2025-02-26 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 18:09 [PATCHv6 0/6] ublk zero copy support Keith Busch
2025-02-26 18:09 ` [PATCHv6 1/5] io_uring: add support for kernel registered bvecs Keith Busch
2025-02-26 18:09 ` [PATCHv6 1/6] io_uring/rw: move fixed buffer import to issue path Keith Busch
2025-02-26 18:09 ` [PATCHv6 2/6] io_uring: add support for kernel registered bvecs Keith Busch
2025-02-26 18:09 ` [PATCHv6 2/5] nvme: map uring_cmd data even if address is 0 Keith Busch
2025-02-26 18:09 ` [PATCHv6 3/6] " Keith Busch
2025-02-26 18:09 ` [PATCHv6 3/5] ublk: zc register/unregister bvec Keith Busch
2025-02-26 18:09 ` [PATCHv6 4/5] io_uring: add abstraction for buf_table rsrc data Keith Busch
2025-02-26 18:09 ` [PATCHv6 4/6] ublk: zc register/unregister bvec Keith Busch
2025-02-26 18:10 ` [PATCHv6 5/6] io_uring: add abstraction for buf_table rsrc data Keith Busch
2025-02-26 18:10 ` [PATCHv6 5/5] io_uring: cache nodes and mapped buffers Keith Busch
2025-02-26 18:10 ` [PATCHv6 6/6] " Keith Busch
2025-02-26 18:17 ` Keith Busch [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=Z79auss5rprO8Dwp@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=bernd@bsbernd.com \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
/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