From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 4.20
Date: Fri, 30 Nov 2018 08:26:33 -0800 [thread overview]
Message-ID: <20181130162633.GA16933@infradead.org> (raw)
In-Reply-To: <01b6314c-903e-6787-ccf6-e93aa789199a@kernel.dk>
On Fri, Nov 30, 2018@08:26:24AM -0700, Jens Axboe wrote:
> On 11/30/18 8:24 AM, Christoph Hellwig wrote:
> > Various fixlets all over, including throwing in a 'default y' for the
> > multipath code, given that we want people to actually enable it for full
> > functionality.
>
> Why enable it by default? 99.9% of users aren't going to care. That
> seems like an odd choice.
Because its small, and if you don't have it you are going to run into
problems pretty soon.
Anyway, to get the fixes out ASAP here is the updated request without
it:
The following changes since commit 14b04063cc994effc86f976625bf8f806d8d44cb:
Merge branch 'nvme-4.20' of git://git.infradead.org/nvme into for-linus (2018-11-21 05:56:28 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.20
for you to fetch changes up to 6344d02dc8f886b6bbcd922ae1a17e4a41500f2d:
nvme-rdma: fix double freeing of async event data (2018-11-30 17:23:23 +0100)
----------------------------------------------------------------
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
Keith Busch (1):
nvme: Free ctrl device name on init failure
Prabhath Sajeepa (1):
nvme-rdma: fix double freeing of async event data
Sagi Grimberg (1):
nvme: flush namespace scanning work just before removing namespaces
drivers/nvme/host/core.c | 8 +++++---
drivers/nvme/host/fc.c | 2 +-
drivers/nvme/host/nvme.h | 3 +++
drivers/nvme/host/rdma.c | 2 ++
4 files changed, 11 insertions(+), 4 deletions(-)
next prev parent reply other threads:[~2018-11-30 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 15:24 [GIT PULL] nvme fixes for 4.20 Christoph Hellwig
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:37 ` Keith Busch
2018-11-30 16:26 ` Christoph Hellwig [this message]
2018-11-30 17:12 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2018-12-07 15:38 Christoph Hellwig
2018-12-07 15:40 ` Jens Axboe
2018-11-09 6:56 Christoph Hellwig
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:29 ` Jens Axboe
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:12 ` Jens Axboe
2018-11-02 6:37 Christoph Hellwig
2018-11-02 14:15 ` 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=20181130162633.GA16933@infradead.org \
--to=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).