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 fixes for 5.11
Date: Thu, 4 Feb 2021 16:07:38 +0100 [thread overview]
Message-ID: <YBwNukLwQfsXQL9U@infradead.org> (raw)
The following changes since commit cd92cdb9c8bcfc27a8f28bcbf7c414a0ea79e5ec:
null_blk: cleanup zoned mode initialization (2021-01-29 07:49:22 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.11
for you to fetch changes up to cb8563f5c735a042ea2dd7df1ad55ae06d63ffeb:
nvmet-tcp: fix out-of-bounds access when receiving multiple h2cdata PDUs (2021-02-03 16:57:36 +0100)
----------------------------------------------------------------
Claus Stovgaard (1):
nvme-pci: ignore the subsysem NQN on Phison E16
Keith Busch (1):
update the email address for Keith Bush
Sagi Grimberg (1):
nvmet-tcp: fix out-of-bounds access when receiving multiple h2cdata PDUs
Thorsten Leemhuis (1):
nvme-pci: avoid the deepest sleep state on Kingston A2000 SSDs
.mailmap | 2 ++
drivers/nvme/host/pci.c | 4 ++++
drivers/nvme/target/tcp.c | 3 ++-
3 files changed, 8 insertions(+), 1 deletion(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-02-04 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 15:07 Christoph Hellwig [this message]
2021-02-04 15:25 ` [GIT PULL] nvme fixes for 5.11 Jens Axboe
2021-02-04 15:27 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2021-01-28 18:56 Christoph Hellwig
2021-01-28 18:58 ` Jens Axboe
2021-01-21 8:32 Christoph Hellwig
2021-01-21 12:41 ` Jens Axboe
2021-01-14 19:29 Christoph Hellwig
2021-01-15 2:48 ` Jens Axboe
2021-01-07 17:42 Christoph Hellwig
2021-01-07 17:58 ` 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=YBwNukLwQfsXQL9U@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