From: Greg KH <greg@kroah.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Subject: Re: Patch "btrfs: also add stripe entries for NOCOW writes" has been added to the 6.11-stable tree
Date: Mon, 28 Oct 2024 06:53:15 +0100 [thread overview]
Message-ID: <2024102809-improving-footwear-bd85@gregkh> (raw)
In-Reply-To: <3e66a465-6502-48d7-b031-1619052a1e66@wdc.com>
On Thu, Oct 24, 2024 at 11:22:16AM +0000, Johannes Thumshirn wrote:
> On 24.10.24 13:17, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > btrfs: also add stripe entries for NOCOW writes
> >
> > to the 6.11-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > btrfs-also-add-stripe-entries-for-nocow-writes.patch
> > and it can be found in the queue-6.11 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
>
> Hey Sasha,
>
> this patch is for the RAID stripe-tree feature marked as experimental,
> so I don't think it's needed to be backported, as noone should use it
> (apart from testing).
Now dropped, thanks.
greg k-h
prev parent reply other threads:[~2024-10-28 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241024111713.3025523-1-sashal@kernel.org>
2024-10-24 11:22 ` Patch "btrfs: also add stripe entries for NOCOW writes" has been added to the 6.11-stable tree Johannes Thumshirn
2024-10-28 5:53 ` Greg KH [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=2024102809-improving-footwear-bd85@gregkh \
--to=greg@kroah.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=stable-commits@vger.kernel.org \
--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