From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fix for 4.18
Date: Fri, 29 Jun 2018 14:40:40 +0200 [thread overview]
Message-ID: <20180629124040.GA3573@infradead.org> (raw)
The following changes since commit 15bfd21fbc5d35834b9ea383dc458a1f0c9e3434:
block: Fix transfer when chunk sectors exceeds max (2018-06-26 12:18:27 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.18
for you to fetch changes up to 682630f00a219a1b0696abe9c0967e660068187b:
nvme-rdma: fix possible double free of controller async event buffer (2018-06-28 16:29:54 +0200)
----------------------------------------------------------------
Sagi Grimberg (1):
nvme-rdma: fix possible double free of controller async event buffer
drivers/nvme/host/rdma.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2018-06-29 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 12:40 Christoph Hellwig [this message]
2018-06-29 13:56 ` [GIT PULL] nvme fix for 4.18 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=20180629124040.GA3573@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--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