From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: [GIT PULL] nvme fixes for Linux 6.7
Date: Fri, 1 Dec 2023 09:02:16 -0700 [thread overview]
Message-ID: <ZWoDiHfUgBs0riE6@kbusch-mbp> (raw)
The following changes since commit bb6cc253861bd5a7cf8439e2118659696df9619f:
bcache: revert replacing IS_ERR_OR_NULL with IS_ERR (2023-11-24 09:39:03 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.7-2023-12-01
for you to fetch changes up to 74fbc88e161424b3b96a22b23a8e3e1edab9d05c:
nvme-core: check for too small lba shift (2023-12-01 07:49:50 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.7
- Invalid namespace identification error handling (Marizio, Ewan, Keith)
- Fabrics keep-alive tuning (Mark)
----------------------------------------------------------------
Ewan D. Milne (1):
nvme: check for valid nvme_identify_ns() before using it
Keith Busch (1):
nvme-core: check for too small lba shift
Mark O'Donovan (1):
nvme: fine-tune sending of first keep-alive
Maurizio Lombardi (1):
nvme-core: fix a memory leak in nvme_ns_info_from_identify()
drivers/nvme/host/core.c | 34 ++++++++++++++++++++++++++++------
1 file changed, 28 insertions(+), 6 deletions(-)
next reply other threads:[~2023-12-01 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 16:02 Keith Busch [this message]
2023-12-01 16:09 ` [GIT PULL] nvme fixes for Linux 6.7 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2023-12-07 17:06 Keith Busch
2023-12-07 17:31 ` Jens Axboe
2023-12-21 21:30 Keith Busch
2023-12-21 21:33 ` 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=ZWoDiHfUgBs0riE6@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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