From: Greg KH <gregkh@linuxfoundation.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH STABLE 4.9 5.4 0/2] btrfs: raid56 backports to reduce destructive RMW
Date: Tue, 9 Aug 2022 07:49:37 +0200 [thread overview]
Message-ID: <YvH1cU3XZLI093KZ@kroah.com> (raw)
In-Reply-To: <02c30c99-b469-7b55-ddf2-7cff177e40ce@gmx.com>
On Tue, Aug 09, 2022 at 06:28:06AM +0800, Qu Wenruo wrote:
>
>
> On 2022/8/8 21:43, Greg KH wrote:
> > On Thu, Aug 04, 2022 at 03:54:17PM +0800, Qu Wenruo wrote:
> > > Hi Greg and Sasha,
> > >
> > > This two patches are backports for stable branchs from v4.9 to v5.4.
> >
> > Please note that these commits are not even in a public release from
> > Linus yet, so I would need a LOT of assurance from the BTRFS maintainers
> > that they are all allowed to be taken now as that goes against the
> > normal development cycle here.
>
> Does this mean, normally backports only happen after a full release, not
> just after -rc releases?
After a -rc release.
next prev parent reply other threads:[~2022-08-09 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 7:54 [PATCH STABLE 4.9 5.4 0/2] btrfs: raid56 backports to reduce destructive RMW Qu Wenruo
2022-08-04 7:54 ` [PATCH STABLE 4.9 5.4 1/2] btrfs: only write the sectors in the vertical stripe which has data stripes Qu Wenruo
2022-08-04 7:54 ` [PATCH STABLE 4.9 5.4 2/2] btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Qu Wenruo
2022-08-08 13:43 ` [PATCH STABLE 4.9 5.4 0/2] btrfs: raid56 backports to reduce destructive RMW Greg KH
2022-08-08 22:28 ` Qu Wenruo
2022-08-09 5:49 ` Greg KH [this message]
2022-08-09 6:08 ` Qu Wenruo
2022-08-09 6:38 ` Greg KH
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=YvH1cU3XZLI093KZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=stable@vger.kernel.org \
--cc=wqu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.