From: Greg KH <gregkh@linuxfoundation.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH STABLE 5.18 0/2] btrfs: raid56 backports to reduce destructive RMW
Date: Sat, 13 Aug 2022 15:13:58 +0200 [thread overview]
Message-ID: <Yvejlr1Nds8wtyKj@kroah.com> (raw)
In-Reply-To: <YvESBmvjMqIXvqjp@kroah.com>
On Mon, Aug 08, 2022 at 03:39:18PM +0200, Greg KH wrote:
> On Thu, Aug 04, 2022 at 04:10:57PM +0800, Qu Wenruo wrote:
> > Hi Greg and Sasha,
> >
> > This two patches are backports for v5.18 branch.
>
> I also need these for the 5.19.y branch if we were to take them into
> 5.18.y as you do not want anyone to suffer a regression when moving to
> the newer kernel release.
>
> So I'll wait for those to be sent before taking any of these.
I've dropped all of these btrfs backports from my "to review" queue now.
Please fix them all up, get the needed acks, and then resend them and I
will be glad to reconsider them at that point in time.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-13 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 8:10 [PATCH STABLE 5.18 0/2] btrfs: raid56 backports to reduce destructive RMW Qu Wenruo
2022-08-04 8:10 ` [PATCH STABLE 5.18 1/2] btrfs: only write the sectors in the vertical stripe which has data stripes Qu Wenruo
2022-08-04 8:10 ` [PATCH STABLE 5.18 2/2] btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Qu Wenruo
2022-08-04 23:28 ` [PATCH STABLE 5.18 0/2] btrfs: raid56 backports to reduce destructive RMW Qu Wenruo
2022-08-08 13:39 ` Greg KH
2022-08-13 13:13 ` Greg KH [this message]
2022-08-13 22:17 ` Qu Wenruo
2022-08-17 16:23 ` David Sterba
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=Yvejlr1Nds8wtyKj@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox