From: Kanchan Joshi <joshi.k@samsung.com>
To: Jens Axboe <axboe@kernel.dk>, Keith Busch <kbusch@meta.com>,
io-uring@vger.kernel.org
Cc: Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] liburing/io_passthrough: use metadata if format requires it
Date: Fri, 18 Apr 2025 10:17:47 +0530 [thread overview]
Message-ID: <e047580f-d7b2-4a14-9b6f-6653d7ed01a7@samsung.com> (raw)
In-Reply-To: <67cffda3-c211-419c-8e49-cf38def85b63@kernel.dk>
On 4/17/2025 11:28 PM, Jens Axboe wrote:
> Confused, there should be zero overlap between this patch and the
> posted one?
Since you are able to apply fine, I must have hallucinated. Sorry for
the fuss.
next prev parent reply other threads:[~2025-04-18 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250416162937epcas5p462a7895320769fbf9f5011c104def842@epcas5p4.samsung.com>
2025-04-16 16:28 ` [PATCH] liburing/io_passthrough: use metadata if format requires it Keith Busch
2025-04-17 14:51 ` Kanchan Joshi
2025-04-17 17:58 ` Jens Axboe
2025-04-18 4:47 ` Kanchan Joshi [this message]
2025-04-17 17:58 ` 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=e047580f-d7b2-4a14-9b6f-6653d7ed01a7@samsung.com \
--to=joshi.k@samsung.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.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