From: Christoph Hellwig <hch@lst.de>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
yi.zhang@redhat.com, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org, yukuai3@huawei.com,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com
Subject: Re: [PATCH] nvme: clear nvme request for nonready request
Date: Mon, 14 Jul 2025 15:42:31 +0200 [thread overview]
Message-ID: <20250714134231.GA11132@lst.de> (raw)
In-Reply-To: <20250628064634.3823093-1-yukuai1@huaweicloud.com>
Are you going to resend this with the feedback from Sagi taken into
account?
next prev parent reply other threads:[~2025-07-14 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 6:46 [PATCH] nvme: clear nvme request for nonready request Yu Kuai
2025-06-28 10:13 ` Sagi Grimberg
2025-07-14 13:42 ` Christoph Hellwig [this message]
2025-07-15 1:08 ` Yu Kuai
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=20250714134231.GA11132@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=johnny.chenyi@huawei.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yi.zhang@redhat.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).