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.8
Date: Thu, 8 Feb 2024 13:26:24 -0800 [thread overview]
Message-ID: <ZcVHAP3H2E-8BpUb@kbusch-mbp> (raw)
The following changes since commit 373581643d3d6f34f16389b481b1462c8cbd37c7:
Merge tag 'nvme-6.8-2024-02-01' of git://git.infradead.org/nvme into block-6.8 (2024-02-01 09:11:02 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme tags/nvme-6.8-2023-02-08
for you to fetch changes up to 4054705215ad7e6dd8e4e6ff27c39abd7667f700:
nvme: use ns->head->pi_size instead of t10_pi_tuple structure size (2024-02-07 15:49:36 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.8
- Update a potentially stale firmware attribute (Maurizio)
- Fixes for the recent verbose error logging (Keith, Chaitanya)
- Protection information payload size fix for passthrough (Francis)
----------------------------------------------------------------
Chaitanya Kulkarni (1):
nvme-core: fix comment to reflect right functions
Francis Pravin (1):
nvme: use ns->head->pi_size instead of t10_pi_tuple structure size
Keith Busch (1):
nvme: move passthrough logging attribute to head
Maurizio Lombardi (1):
nvme-host: fix the updating of the firmware version
drivers/nvme/host/core.c | 14 ++++++++------
drivers/nvme/host/ioctl.c | 2 +-
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/host/sysfs.c | 30 +++++++++++++++---------------
4 files changed, 25 insertions(+), 23 deletions(-)
next reply other threads:[~2024-02-08 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 21:26 Keith Busch [this message]
2024-02-08 22:05 ` [GIT PULL] nvme fixes for Linux 6.8 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 16:09 Keith Busch
2024-02-15 16:42 ` Jens Axboe
2024-02-01 16:03 Keith Busch
2024-02-01 16:11 ` 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=ZcVHAP3H2E-8BpUb@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