From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 5.3
Date: Thu, 25 Jul 2019 10:24:25 -0600 [thread overview]
Message-ID: <f1bda303-27f9-8c5c-3cb1-a2bb58c91566@kernel.dk> (raw)
In-Reply-To: <20190725141245.GA4339@infradead.org>
On 7/25/19 8:12 AM, Christoph Hellwig wrote:
>
> The following changes since commit 77ce56e2bfaa64127ae5e23ef136c0168b818777:
>
> drbd: dynamically allocate shash descriptor (2019-07-23 07:35:18 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git nvme-5.3
>
> for you to fetch changes up to 8fe34be14ecb5eb0ef8d8d44aa7ab62d9e2911ca:
>
> Revert "nvme-pci: don't create a read hctx mapping without read queues" (2019-07-23 17:47:02 +0200)
>
> ----------------------------------------------------------------
> Logan Gunthorpe (1):
> nvme: fix memory leak caused by incorrect subsystem free
>
> Marta Rybczynska (1):
> nvme: fix multipath crash when ANA is deactivated
>
> Misha Nasledov (1):
> nvme: ignore subnqn for ADATA SX6000LNP
>
> yangerkun (1):
> Revert "nvme-pci: don't create a read hctx mapping without read queues"
>
> drivers/nvme/host/core.c | 12 +++++-------
> drivers/nvme/host/multipath.c | 8 ++------
> drivers/nvme/host/nvme.h | 6 +++++-
> drivers/nvme/host/pci.c | 6 +++---
> 4 files changed, 15 insertions(+), 17 deletions(-)
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2019-07-25 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 14:12 [GIT PULL] nvme fixes for 5.3 Christoph Hellwig
2019-07-25 16:24 ` 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=f1bda303-27f9-8c5c-3cb1-a2bb58c91566@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--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