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.12
Date: Fri, 13 Sep 2024 08:34:04 -0600 [thread overview]
Message-ID: <ZuRNXAVHqQJngQKe@kbusch-mbp> (raw)
Sending a follow up sooner than usual: the important fix here is for a
potential build error for certain configs.
The following changes since commit 68f31e88917f5608eb8da0bef37249648ffd48d4:
Merge tag 'md-6.12-20240906' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into for-6.12/block (2024-09-06 14:43:16 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.12-2024-09-13
for you to fetch changes up to 83bdfcbdbe5d901c5fa432decf12e1725a840a56:
nvme-pci: qdepth 1 quirk (2024-09-13 07:29:30 -0700)
----------------------------------------------------------------
nvme fixes for Linux 6.12
- A syntax cleanup (Shen)
- Fix a Kconfig linking error (Arnd)
- New queue-depth quirk (Keith)
----------------------------------------------------------------
Arnd Bergmann (1):
nvme-tcp: fix link failure for TCP auth
Keith Busch (1):
nvme-pci: qdepth 1 quirk
Shen Lichuan (1):
nvme: Convert comma to semicolon
drivers/nvme/host/Kconfig | 2 +-
drivers/nvme/host/core.c | 2 +-
drivers/nvme/host/nvme.h | 5 +++++
drivers/nvme/host/pci.c | 18 +++++++++---------
4 files changed, 16 insertions(+), 11 deletions(-)
next reply other threads:[~2024-09-13 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 14:34 Keith Busch [this message]
2024-09-13 14:39 ` [GIT PULL] nvme fixes for linux 6.12 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-09-25 6:40 [GIT PULL] nvme fixes for Linux 6.12 Keith Busch
2024-09-25 9:29 ` Jens Axboe
2024-10-17 18:48 Keith Busch
2024-10-17 19:12 ` Jens Axboe
2024-10-31 15:08 Keith Busch
2024-10-31 15:10 ` 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=ZuRNXAVHqQJngQKe@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