From: Dave Hansen <dave.hansen@intel.com>
To: Anand Suveer Jain <asj@kernel.org>, linux-btrfs@vger.kernel.org
Cc: dwmw2@infradead.org, thiago.macieira@intel.com, dsterba@suse.cz
Subject: Re: [PATCH] btrfs: derive f_fsid with dev_t only when temp_fsid is active
Date: Sat, 12 Sep 2026 18:13:20 -0700 [thread overview]
Message-ID: <be9be757-0714-46a8-abe8-e7046fba0d7c@intel.com> (raw)
In-Reply-To: <895570e1-4d79-416e-b558-2e61d04adff3@kernel.org>
On 9/12/26 18:05, Anand Suveer Jain wrote:
...
>> BTW, this is hitting folks running 7.2, iirc. Could whoever commits it
>> and sends it up to Linus tag it for stable, please?
>
> The patch includes the Fixes: tag, so once it merges into mainline,
> it should be queued for the stable releases shortly after.
Did something change there? Or is there something special about fs/ or
btrfs here? I know Sasha's scripts tend to go out and magically find
things. But I thought the best (and only documented) process was still
to add explicit stable tags.
Documentation/process/stable-kernel-rules.rst doesn't say anywhere that
I can see that a Fixes tag along is sufficient.
If you're right, then awesome! I can forget about Cc:stable@ and just
focus on Fixes: tags alone.
next prev parent reply other threads:[~2026-09-13 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 18:06 [PATCH] btrfs: derive f_fsid with dev_t only when temp_fsid is active Anand Jain
2026-09-12 21:58 ` Dave Hansen
2026-09-13 1:05 ` Anand Suveer Jain
2026-09-13 1:13 ` Dave Hansen [this message]
2026-09-13 2:43 ` Anand Suveer Jain
2026-09-14 3:42 ` Anand Suveer Jain
2026-09-14 5:28 ` David Woodhouse
2026-09-14 8:28 ` Anand Suveer Jain
2026-09-14 10:47 ` David Woodhouse
2026-09-14 12:28 ` Anand Suveer Jain
2026-09-14 16:41 ` David Sterba
2026-09-14 16:39 ` David Sterba
2026-09-14 16:46 ` David Sterba
2026-09-18 8:59 ` Anand Suveer Jain
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=be9be757-0714-46a8-abe8-e7046fba0d7c@intel.com \
--to=dave.hansen@intel.com \
--cc=asj@kernel.org \
--cc=dsterba@suse.cz \
--cc=dwmw2@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=thiago.macieira@intel.com \
/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