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.20
Date: Fri, 9 Nov 2018 07:56:54 +0100 [thread overview]
Message-ID: <20181109065654.GA12805@infradead.org> (raw)
- revert an RDMA commit that didn't help but caused problems
- fix another minor P2P fallout
- make sure the multipath device inherits the devices limits of
the controllers below
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.20
for you to fetch changes up to 72e43e497b07d607142f07a8c56794261fbe089b:
Revert "nvmet-rdma: use a private workqueue for delete" (2018-11-07 09:27:22 +0100)
----------------------------------------------------------------
Christoph Hellwig (1):
Revert "nvmet-rdma: use a private workqueue for delete"
Sagi Grimberg (2):
nvmet: don't try to add ns to p2p map unless it actually uses it
nvme: make sure ns head inherits underlying device limits
drivers/nvme/host/core.c | 4 +++-
drivers/nvme/host/multipath.c | 1 +
drivers/nvme/target/core.c | 2 +-
drivers/nvme/target/rdma.c | 19 ++++---------------
4 files changed, 9 insertions(+), 17 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 4.20
Date: Fri, 9 Nov 2018 07:56:54 +0100 [thread overview]
Message-ID: <20181109065654.GA12805@infradead.org> (raw)
- revert an RDMA commit that didn't help but caused problems
- fix another minor P2P fallout
- make sure the multipath device inherits the devices limits of
the controllers below
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.20
for you to fetch changes up to 72e43e497b07d607142f07a8c56794261fbe089b:
Revert "nvmet-rdma: use a private workqueue for delete" (2018-11-07 09:27:22 +0100)
----------------------------------------------------------------
Christoph Hellwig (1):
Revert "nvmet-rdma: use a private workqueue for delete"
Sagi Grimberg (2):
nvmet: don't try to add ns to p2p map unless it actually uses it
nvme: make sure ns head inherits underlying device limits
drivers/nvme/host/core.c | 4 +++-
drivers/nvme/host/multipath.c | 1 +
drivers/nvme/target/core.c | 2 +-
drivers/nvme/target/rdma.c | 19 ++++---------------
4 files changed, 9 insertions(+), 17 deletions(-)
next reply other threads:[~2018-11-09 6:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 6:56 Christoph Hellwig [this message]
2018-11-09 6:56 ` [GIT PULL] nvme fixes for 4.20 Christoph Hellwig
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:29 ` Jens Axboe
2018-11-09 13:29 ` Jens Axboe
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:12 ` Jens Axboe
2018-11-09 17:12 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2018-12-07 15:38 Christoph Hellwig
2018-12-07 15:38 ` Christoph Hellwig
2018-12-07 15:40 ` Jens Axboe
2018-12-07 15:40 ` Jens Axboe
2018-11-30 15:24 Christoph Hellwig
2018-11-30 15:24 ` Christoph Hellwig
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:37 ` Keith Busch
2018-11-30 15:37 ` Keith Busch
2018-11-30 16:26 ` Christoph Hellwig
2018-11-30 16:26 ` Christoph Hellwig
2018-11-30 17:12 ` Jens Axboe
2018-11-30 17:12 ` Jens Axboe
2018-11-02 6:37 Christoph Hellwig
2018-11-02 6:37 ` Christoph Hellwig
2018-11-02 14:15 ` Jens Axboe
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=20181109065654.GA12805@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 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.