From: Jens Axboe <axboe@kernel.dk>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-block@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] second round of nvme updates for 5.4
Date: Thu, 12 Sep 2019 11:20:41 -0600 [thread overview]
Message-ID: <19027784-22ec-e479-b963-ae6b1c93fdd0@kernel.dk> (raw)
In-Reply-To: <20190912164151.7788-1-sagi@grimberg.me>
On 9/12/19 10:41 AM, Sagi Grimberg wrote:
> Hey Jens,
>
> This is the second batch of nvme updates for 5.4.
>
> Highlights includes:
> - controller reset and namespace scan races fixes
> - nvme discovery log change uevent support
> - naming improvements from Keith
> - multiple discovery controllers reject fix from James
> - some regular cleanups from various people
Thanks Sagi, pulled.
--
Jens Axboe
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-09-12 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 16:41 [GIT PULL] second round of nvme updates for 5.4 Sagi Grimberg
2019-09-12 17:20 ` Jens Axboe [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=19027784-22ec-e479-b963-ae6b1c93fdd0@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).