From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>,
James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH v2 0/2] Fix missing AENs when discovery controllers are disconnected
Date: Tue, 27 Sep 2022 09:18:23 +0200 [thread overview]
Message-ID: <20220927071823.GA16121@lst.de> (raw)
In-Reply-To: <20220922081538.13364-1-sagi@grimberg.me>
Thanks,
applied to nvme-6.1 after fixing up the bit positions.
next prev parent reply other threads:[~2022-09-27 7:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 8:15 [PATCH v2 0/2] Fix missing AENs when discovery controllers are disconnected Sagi Grimberg
2022-09-22 8:15 ` [PATCH v2 1/2] nvme: enumerate controller flags Sagi Grimberg
2022-09-22 8:34 ` Daniel Wagner
2022-09-22 15:05 ` James Smart
2022-09-22 15:25 ` Keith Busch
2022-09-22 8:15 ` [PATCH v2 2/2] nvme: send a rediscover uevent when a persistent discovery controller reconnects Sagi Grimberg
2022-09-22 8:30 ` Daniel Wagner
2022-09-22 8:33 ` Sagi Grimberg
2022-09-22 8:34 ` Daniel Wagner
2022-09-22 8:36 ` Daniel Wagner
2022-09-22 15:05 ` James Smart
2022-09-22 8:15 ` [PATCH v2 3/2 nvme-cli] fabrics: re-read the discovery log page when a discovery controller reconnected Sagi Grimberg
2022-09-22 8:37 ` Daniel Wagner
2022-09-22 15:06 ` James Smart
2022-09-27 7:52 ` Daniel Wagner
2022-09-27 10:50 ` Belanger, Martin
2022-09-27 11:22 ` Daniel Wagner
2022-09-27 11:59 ` Daniel Wagner
2022-09-27 7:18 ` Christoph Hellwig [this message]
2022-09-28 6:47 ` [PATCH v2 0/2] Fix missing AENs when discovery controllers are disconnected Sagi Grimberg
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=20220927071823.GA16121@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@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