From: Jens Axboe <axboe@fb.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
<linux-nvme@lists.infradead.org>, <linux-block@vger.kernel.org>
Subject: Re: [GIT PULL] nvme fixes for 5.7
Date: Fri, 8 May 2020 09:49:41 -0600 [thread overview]
Message-ID: <ef6d2cf7-4a21-d4e9-3303-979411d50ea4@fb.com> (raw)
In-Reply-To: <20200508153951.GA250474@infradead.org>
On 5/8/20 9:39 AM, Christoph Hellwig wrote:
> The following changes since commit 860a93ff87acd001eea827b70f4a7a64c0854b81:
>
> bdi: add a ->dev_name field to struct backing_dev_info (2020-05-07 08:45:47 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git nvme-5.7
>
> for you to fetch changes up to 8874d040ff34285e8b8458a75f9434e19ed06174:
>
> nvme: fix possible hang when ns scanning fails during error recovery (2020-05-08 17:04:15 +0200)
>
> ----------------------------------------------------------------
> Alexey Dobriyan (1):
> nvme-pci: fix "slimmer CQ head update"
>
> Sagi Grimberg (1):
> nvme: fix possible hang when ns scanning fails during error recovery
>
> drivers/nvme/host/core.c | 2 +-
> drivers/nvme/host/pci.c | 6 +++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2020-05-08 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 15:39 [GIT PULL] nvme fixes for 5.7 Christoph Hellwig
2020-05-08 15:49 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-08 6:21 Christoph Hellwig
2020-04-08 14:41 ` Jens Axboe
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=ef6d2cf7-4a21-d4e9-3303-979411d50ea4@fb.com \
--to=axboe@fb.com \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--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).