From: Sasha Levin <sashal@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
Mikhail Dmitrichenko <mdmitrichenko@astralinux.ru>,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH 6.12] bcachefs: avoid truncating fiemap extent length
Date: Sun, 5 Jul 2026 10:33:48 -0400 [thread overview]
Message-ID: <2026070510-stable-reply-bcachefs-fiemap@kernel.org> (raw)
In-Reply-To: <akkdYigsmB8tJf6T@shelob>
On Sat, Jul 04, 2026 at 09:49:11AM -0500, Kent Overstreet wrote:
>On Fri, Jul 03, 2026 at 10:05:22PM -0400, Sasha Levin wrote:
>> Thanks for the patch, happy to take it if we can get an ack from the bcachefs
>> maintainers.
>
>Ack
Queued for 6.12, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-05 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 11:48 [PATCH 6.12] bcachefs: avoid truncating fiemap extent length Mikhail Dmitrichenko
2026-07-04 2:05 ` Sasha Levin
2026-07-04 14:49 ` Kent Overstreet
2026-07-05 14:33 ` Sasha Levin [this message]
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=2026070510-stable-reply-bcachefs-fiemap@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mdmitrichenko@astralinux.ru \
--cc=stable@vger.kernel.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