From: Sagi Grimberg <sagi@grimberg.me>
To: Keith Busch <kbusch@fb.com>, linux-nvme@lists.infradead.org, hch@lst.de
Cc: Keith Busch <kbusch@kernel.org>, Jeff Lien <jeff.lien@wdc.com>
Subject: Re: [PATCH] nvme: copy firmware_rev on each init
Date: Tue, 20 Sep 2022 11:23:06 +0300 [thread overview]
Message-ID: <221a606f-2be5-b950-f0a0-1d8098f663c3@grimberg.me> (raw)
In-Reply-To: <20220919194508.1704346-1-kbusch@fb.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2022-09-20 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 19:45 [PATCH] nvme: copy firmware_rev on each init Keith Busch
2022-09-19 23:04 ` Chaitanya Kulkarni
2022-09-20 8:23 ` Sagi Grimberg [this message]
2022-09-21 1:48 ` Chao Leng
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=221a606f-2be5-b950-f0a0-1d8098f663c3@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@lst.de \
--cc=jeff.lien@wdc.com \
--cc=kbusch@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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.