From: Christoph Hellwig <hch@infradead.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH v3] nvme: revalidate paths during rescan
Date: Tue, 24 Aug 2021 15:00:09 +0100 [thread overview]
Message-ID: <YST7adHFG0XLlPVG@infradead.org> (raw)
In-Reply-To: <20210824134830.gdl4vojwhlsoypne@carbon.lan>
On Tue, Aug 24, 2021 at 03:48:30PM +0200, Daniel Wagner wrote:
> I am blind. The patch is queued up in nvme-5.15.
>
> @Christoph, do you want me to send fix on top of this patch or do you
> want an updated version of this patch?
Either way is fine.
prev parent reply other threads:[~2021-08-24 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 15:28 [PATCH v3] nvme: revalidate paths during rescan Daniel Wagner
2021-08-18 12:44 ` Daniel Wagner
2021-08-23 8:00 ` Christoph Hellwig
2021-08-23 17:16 ` Sagi Grimberg
2021-08-24 13:44 ` Daniel Wagner
2021-08-24 13:48 ` Daniel Wagner
2021-08-24 14:00 ` Christoph Hellwig [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=YST7adHFG0XLlPVG@infradead.org \
--to=hch@infradead.org \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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