From: Christoph Hellwig <hch@infradead.org>
To: axboe@fb.com
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fix for 5.7
Date: Thu, 28 May 2020 15:22:31 +0200 [thread overview]
Message-ID: <20200528132231.GA837884@infradead.org> (raw)
The following changes since commit b69e2ef24b7b4867f80f47e2781e95d0bacd15cb:
nvme-pci: dma read memory barrier for completions (2020-05-12 18:02:24 +0200)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.7
for you to fetch changes up to 9210c075cef29c1f764b4252f93105103bdfb292:
nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll() (2020-05-27 20:32:56 +0200)
----------------------------------------------------------------
Dongli Zhang (1):
nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll()
drivers/nvme/host/pci.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: axboe@fb.com
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fix for 5.7
Date: Thu, 28 May 2020 15:22:31 +0200 [thread overview]
Message-ID: <20200528132231.GA837884@infradead.org> (raw)
The following changes since commit b69e2ef24b7b4867f80f47e2781e95d0bacd15cb:
nvme-pci: dma read memory barrier for completions (2020-05-12 18:02:24 +0200)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.7
for you to fetch changes up to 9210c075cef29c1f764b4252f93105103bdfb292:
nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll() (2020-05-27 20:32:56 +0200)
----------------------------------------------------------------
Dongli Zhang (1):
nvme-pci: avoid race between nvme_reap_pending_cqes() and nvme_poll()
drivers/nvme/host/pci.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-05-28 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 13:22 Christoph Hellwig [this message]
2020-05-28 13:22 ` [GIT PULL] nvme fix for 5.7 Christoph Hellwig
2020-05-28 14:48 ` Jens Axboe
2020-05-28 14:48 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2020-05-16 13:25 Christoph Hellwig
2020-05-16 13:25 ` Christoph Hellwig
2020-05-16 15:26 ` Jens Axboe
2020-05-16 15:26 ` Jens Axboe
2020-04-30 15:28 Christoph Hellwig
2020-04-30 15:28 ` Christoph Hellwig
2020-04-30 15:33 ` Jens Axboe
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=20200528132231.GA837884@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.