From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 6.15-final
Date: Thu, 22 May 2025 13:58:14 -0600 [thread overview]
Message-ID: <75e87d71-b83f-40b1-9f60-dc3747fc5fc0@kernel.dk> (raw)
Hi Linus,
Two fixes for block that should go into the 6.15 kernel release. Both
introduced in this cycle.
- Fix for a regression with setting up loop on a file system without
->write_iter().
- Fix for an nvme sysfs regression.
Please pull!
The following changes since commit dd24f87f65c957f30e605e44961d2fd53a44c780:
ublk: fix dead loop when canceling io command (2025-05-15 10:53:41 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/block-6.15-20250522
for you to fetch changes up to 115c011f5db7e5f1a1f4404a8f5b5c87a3534362:
Merge tag 'nvme-6.15-2025-05-22' of git://git.infradead.org/nvme into block-6.15 (2025-05-22 09:25:47 -0600)
----------------------------------------------------------------
block-6.15-20250522
----------------------------------------------------------------
Christoph Hellwig (1):
loop: don't require ->write_iter for writable files in loop_configure
Jens Axboe (1):
Merge tag 'nvme-6.15-2025-05-22' of git://git.infradead.org/nvme into block-6.15
Nilay Shroff (1):
nvme: avoid creating multipath sysfs group under namespace path devices
drivers/block/loop.c | 3 ---
drivers/nvme/host/sysfs.c | 28 ++++++++++++++++++++++++++++
2 files changed, 28 insertions(+), 3 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-05-22 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 19:58 Jens Axboe [this message]
2025-05-22 20:16 ` [GIT PULL] Block fixes for 6.15-final pr-tracker-bot
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=75e87d71-b83f-40b1-9f60-dc3747fc5fc0@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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