Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fix for 5.7
Date: Sat, 16 May 2020 09:26:04 -0600	[thread overview]
Message-ID: <b693162e-0a1b-10be-6d49-fb278d27dc8a@kernel.dk> (raw)
In-Reply-To: <20200516132532.GA244143@infradead.org>

On 5/16/20 7:25 AM, Christoph Hellwig wrote:
> The following changes since commit 59c7c3caaaf8750df4ec3255082f15eb4e371514:
> 
>   nvme: fix possible hang when ns scanning fails during error recovery (2020-05-09 16:07:58 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git nvme-5.7
> 
> for you to fetch changes up to b69e2ef24b7b4867f80f47e2781e95d0bacd15cb:
> 
>   nvme-pci: dma read memory barrier for completions (2020-05-12 18:02:24 +0200)
> 
> ----------------------------------------------------------------
> Keith Busch (1):
>       nvme-pci: dma read memory barrier for completions
> 
>  drivers/nvme/host/pci.c | 5 +++++
>  1 file changed, 5 insertions(+)

Pulled, thanks.

-- 
Jens Axboe


_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-05-16 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 13:25 [GIT PULL] nvme fix for 5.7 Christoph Hellwig
2020-05-16 15:26 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-28 13:22 Christoph Hellwig
2020-05-28 14:48 ` Jens Axboe
2020-04-30 15:28 Christoph Hellwig
2020-04-30 15:33 ` 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=b693162e-0a1b-10be-6d49-fb278d27dc8a@kernel.dk \
    --to=axboe@kernel.dk \
    --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