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] second round of nvme updates for Linux 5.16
Date: Thu, 28 Oct 2021 16:27:59 +0200 [thread overview]
Message-ID: <YXqzb6dj0DCrIbGY@infradead.org> (raw)
The following changes since commit d28e4dff085c5a87025c9a0a85fb798bd8e9ca17:
block: ataflop: more blk-mq refactoring fixes (2021-10-25 07:54:32 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.16-2021-10-28
for you to fetch changes up to d156cfcafbd0eae4224ea007d95ebda467eb0c46:
nvmet: use flex_array_size and struct_size (2021-10-27 08:06:41 +0200)
----------------------------------------------------------------
nvme updates for Linux 5.16
- support the current discovery subsystem entry (Hannes Reinecke)
- use flex_array_size and struct_size (Len Baker)
----------------------------------------------------------------
Hannes Reinecke (3):
nvme: add new discovery log page entry definitions
nvmet: switch check for subsystem type
nvmet: register discovery subsystem as 'current'
Len Baker (1):
nvmet: use flex_array_size and struct_size
drivers/nvme/host/multipath.c | 2 +-
drivers/nvme/target/admin-cmd.c | 2 +-
drivers/nvme/target/core.c | 1 +
drivers/nvme/target/discovery.c | 17 +++++++++++------
drivers/nvme/target/nvmet.h | 2 +-
include/linux/nvme.h | 19 ++++++++++++++++---
6 files changed, 31 insertions(+), 12 deletions(-)
next reply other threads:[~2021-10-28 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 14:27 Christoph Hellwig [this message]
2021-10-28 14:35 ` [GIT PULL] second round of nvme updates for Linux 5.16 Jens Axboe
2021-10-29 10:19 ` Hannes Reinecke
2021-10-29 10:32 ` Hannes Reinecke
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=YXqzb6dj0DCrIbGY@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;
as well as URLs for NNTP newsgroup(s).