From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Greg KH" <gregkh@linuxfoundation.org>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: Qu Wenruo <wqu@suse.com>,
stable@vger.kernel.org, linux-btrfs@vger.kernel.org,
David Sterba <dsterba@suse.com>
Subject: Re: [PATCH for v5.15 1/2] btrfs: don't hold CPU for too long when defragging a file
Date: Fri, 18 Feb 2022 08:06:43 +0800 [thread overview]
Message-ID: <72e5d922-dff9-c564-e4f1-11413cc745fd@gmx.com> (raw)
In-Reply-To: <Yg6mplO5BeK5kC7w@kroah.com>
On 2022/2/18 03:48, Greg KH wrote:
> On Thu, Feb 17, 2022 at 08:41:51PM +0100, Holger Hoffstätte wrote:
>> On 2022-02-17 20:01, Greg KH wrote:
>>> On Wed, Feb 16, 2022 at 03:09:07PM +0800, Qu Wenruo wrote:
>>>> commit 2d192fc4c1abeb0d04d1c8cd54405ff4a0b0255b upstream.
>>>
>>> This commit is already in 5.15.22.
>>
>> It most certainly is not
>
> Commit 2d192fc4c1abeb0d04d1c8cd54405ff4a0b0255b is in 5.15.22.
>
>> since it applies cleanly in 5.15.24.
>> The correct upstream commit of this patch is ea0eba69a2a8125229b1b6011644598039bc53aa
>
> Ah, no wonder the confusion. For obvious reasons, I can not take this
> as-is :)
My bad, wrong commit hash...
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2022-02-18 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 7:09 [PATCH for v5.15 0/2] Defrag fixes for v5.15 Qu Wenruo
2022-02-16 7:09 ` [PATCH for v5.15 1/2] btrfs: don't hold CPU for too long when defragging a file Qu Wenruo
2022-02-17 19:01 ` Greg KH
2022-02-17 19:41 ` Holger Hoffstätte
2022-02-17 19:48 ` Greg KH
2022-02-18 0:06 ` Qu Wenruo [this message]
2022-02-16 7:09 ` [PATCH for v5.15 2/2] btrfs: defrag: use the same cluster size for defrag ioctl and autodefrag Qu Wenruo
2022-02-16 12:37 ` David Sterba
2022-02-16 12:49 ` Qu Wenruo
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=72e5d922-dff9-c564-e4f1-11413cc745fd@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=holger@applied-asynchrony.com \
--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