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 fixes for 4.14, take 2
Date: Mon, 11 Sep 2017 14:55:12 -0700 [thread overview]
Message-ID: <20170911215512.GA9661@infradead.org> (raw)
Hi Jens,
below are a few small fixes for the current merge window:
- fix string.h compilation failures with the new memcpy_and_pad
helper (Martin Wilck)
- fix incorrect dereference of a PCI data structure in the lightnvm
support code (me)
- HMB fixes (Akinobu Mita and me)
The following changes since commit 09c2c359be546df45be0b158ea1d3cc8ea83c876:
block: fix integer overflow in __blkdev_sectors_to_bio_pages() (2017-09-11 09:46:49 -0600)
are available in the git repository at:
git://git.infradead.org/nvme.git nvme-4.14
for you to fetch changes up to 1359798f9d4082eb04575efdd19512fbd9c28464:
string.h: un-fortify memcpy_and_pad (2017-09-11 12:29:41 -0400)
----------------------------------------------------------------
Akinobu Mita (1):
nvme-pci: use appropriate initial chunk size for HMB allocation
Christoph Hellwig (4):
nvme: fix lightnvm check
nvme-pci: fix host memory buffer allocation fallback
nvme-pci: propagate (some) errors from host memory buffer setup
nvme-pci: implement the HMB entry number and size limitations
Martin Wilck (1):
string.h: un-fortify memcpy_and_pad
drivers/nvme/host/core.c | 11 ++++---
drivers/nvme/host/lightnvm.c | 26 ----------------
drivers/nvme/host/nvme.h | 13 +++++---
drivers/nvme/host/pci.c | 74 ++++++++++++++++++++++++++++++--------------
include/linux/nvme.h | 4 ++-
include/linux/string.h | 15 ++-------
6 files changed, 70 insertions(+), 73 deletions(-)
next reply other threads:[~2017-09-11 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 21:55 Christoph Hellwig [this message]
2017-09-11 22:00 ` [GIT PULL] nvme fixes for 4.14, take 2 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=20170911215512.GA9661@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;
as well as URLs for NNTP newsgroup(s).