From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme updates for 5.10
Date: Sun, 27 Sep 2020 09:23:43 +0200 [thread overview]
Message-ID: <20200927072343.GA381603@infradead.org> (raw)
The following changes since commit 163090c14a42778c3ccfbdaf39133129bea68632:
Merge branch 'md-next' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into for-5.10/drivers (2020-09-25 07:48:20 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.10-2020-09-27
for you to fetch changes up to 21cc2f3f799fa228f812f7ab971fa8d43c893392:
nvme-pci: allocate separate interrupt for the reserved non-polled I/O queue (2020-09-27 09:14:19 +0200)
----------------------------------------------------------------
nvme updates for 5.10
- fix keep alive timer modification (Amit Engel)
- order the PCI ID list more sensibly (Andy Shevchenko)
- cleanup the open by controller helper (Chaitanya Kulkarni)
- use an xarray for th CSE log lookup (Chaitanya Kulkarni)
- support ZNS in nvmet passthrough mode (Chaitanya Kulkarni)
- fix nvme_ns_report_zones (me)
- add a sanity check to nvmet-fc (James Smart)
- fix interrupt allocation when too many polled queues are specified
(Jeffle Xu)
- small nvmet-tcp optimization (Mark Wunderlich)
----------------------------------------------------------------
Amit Engel (1):
nvmet: handle keep-alive timer when kato is modified by a set features cmd
Andy Shevchenko (1):
nvme-pci: Move enumeration by class to be last in the table
Chaitanya Kulkarni (3):
nvme: lift the file open code from nvme_ctrl_get_by_path
nvme: use an xarray to lookup the Commands Supported and Effects log
nvmet: add passthru ZNS support
Christoph Hellwig (1):
nvme: fix error handling in nvme_ns_report_zones
James Smart (1):
nvmet-fc: fix missing check for no hostport struct
Jeffle Xu (1):
nvme-pci: allocate separate interrupt for the reserved non-polled I/O queue
Mark Wunderlich (1):
nvmet-tcp: have queue io_work context run on sock incoming cpu
drivers/nvme/host/core.c | 56 +++++++----------------------------------
drivers/nvme/host/nvme.h | 4 +--
drivers/nvme/host/pci.c | 35 +++++++++++++-------------
drivers/nvme/host/zns.c | 41 ++++++++++++------------------
drivers/nvme/target/admin-cmd.c | 2 ++
drivers/nvme/target/core.c | 4 +--
drivers/nvme/target/fc.c | 2 +-
drivers/nvme/target/nvmet.h | 2 ++
drivers/nvme/target/passthru.c | 43 +++++++++++++++++++++++--------
drivers/nvme/target/tcp.c | 21 ++++++++--------
10 files changed, 93 insertions(+), 117 deletions(-)
next reply other threads:[~2020-09-27 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 7:23 Christoph Hellwig [this message]
2020-09-28 1:53 ` [GIT PULL] nvme updates for 5.10 Damien Le Moal
2020-09-28 6:03 ` hch
2020-09-28 9:13 ` Damien Le Moal
2020-09-28 15:03 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2020-10-08 14:10 Christoph Hellwig
2020-10-08 14:52 ` Jens Axboe
2020-10-08 14:56 ` Christoph Hellwig
2020-10-08 14:57 ` Jens Axboe
2020-10-08 15:01 Christoph Hellwig
2020-10-08 15:48 ` 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=20200927072343.GA381603@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--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