From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block changes for 4.20-rc5
Date: Sat, 1 Dec 2018 11:43:45 -0700 [thread overview]
Message-ID: <356ff70c-9de6-12f6-ddc1-bb49d0f5df30@kernel.dk> (raw)
Hi Linus,
A set of fixes for the next -rc release. This pull request contains:
- Single range elevator discard merge fix, that caused crashes (Ming)
- Fix for a regression in O_DIRECT, where we could potentially lose the
error value (Maximilian Heyne)
- NVMe pull request from Christoph, with little fixes all over the map
for NVMe.
Please pull!
git://git.kernel.dk/linux-block.git tags/for-linus-20181201
----------------------------------------------------------------
Christoph Hellwig (1):
nvme: warn when finding multi-port subsystems without multipathing enabled
Ewan D. Milne (1):
nvme-fc: initialize nvme_req(rq)->ctrl after calling __nvme_fc_init_request()
Igor Konopko (1):
nvme-pci: fix surprise removal
Jens Axboe (1):
Merge branch 'nvme-4.20' of git://git.infradead.org/nvme into for-linus
Keith Busch (1):
nvme: Free ctrl device name on init failure
Maximilian Heyne (1):
fs: fix lost error code in dio_complete
Ming Lei (1):
block: fix single range discard merge
Prabhath Sajeepa (1):
nvme-rdma: fix double freeing of async event data
Sagi Grimberg (1):
nvme: flush namespace scanning work just before removing namespaces
block/blk-merge.c | 2 +-
drivers/nvme/host/core.c | 8 +++++---
drivers/nvme/host/fc.c | 2 +-
drivers/nvme/host/nvme.h | 3 +++
drivers/nvme/host/rdma.c | 2 ++
fs/direct-io.c | 4 ++--
6 files changed, 14 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2018-12-01 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 18:43 Jens Axboe [this message]
2018-12-01 20:05 ` [GIT PULL] Block changes for 4.20-rc5 pr-tracker-bot
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=356ff70c-9de6-12f6-ddc1-bb49d0f5df30@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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