From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
josef@toxicpanda.com, dsterba@suse.com, martin@lichtvoll.de,
wqu@suse.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] btrfs: do not zero f_bavail if we have available space" failed to apply to 5.5-stable tree
Date: Sun, 9 Feb 2020 10:59:50 -0500 [thread overview]
Message-ID: <20200209155950.GD3584@sasha-vm> (raw)
In-Reply-To: <20200209132640.GA2059551@kroah.com>
On Sun, Feb 09, 2020 at 02:26:40PM +0100, Greg KH wrote:
>On Sun, Feb 09, 2020 at 02:04:21PM +0100, Jiri Slaby wrote:
>> On 09. 02. 20, 12:33, gregkh@linuxfoundation.org wrote:
>> >
>> > The patch below does not apply to the 5.5-stable tree.
>> > If someone wants it applied there, or to any other stable or longterm
>> > tree, then please email the backport, including the original git commit
>> > id to <stable@vger.kernel.org>.
>> >
>> > thanks,
>> >
>> > greg k-h
>> >
>> > ------------------ original commit in Linus's tree ------------------
>> >
>> > From d55966c4279bfc6a0cf0b32bf13f5df228a1eeb6 Mon Sep 17 00:00:00 2001
>> > From: Josef Bacik <josef@toxicpanda.com>
>> > Date: Fri, 31 Jan 2020 09:31:05 -0500
>> > Subject: [PATCH] btrfs: do not zero f_bavail if we have available space
>>
>> 5.5.2 was already released with this patch:
>> commit 165387a9c90152f35976d82feca6eff5f0d5ac02
>> Author: Josef Bacik <josef@toxicpanda.com>
>> Date: Fri Jan 31 09:31:05 2020 -0500
>>
>> btrfs: do not zero f_bavail if we have available space
>>
>> commit d55966c4279bfc6a0cf0b32bf13f5df228a1eeb6 upstream.
>>
>> It cannot be applied twice :).
>
>Oops, Sasha beat me too it, sorry for the noise :)
I've grabbed it for the fixes: tag, sorry :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-09 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 11:33 FAILED: patch "[PATCH] btrfs: do not zero f_bavail if we have available space" failed to apply to 5.5-stable tree gregkh
2020-02-09 13:04 ` Jiri Slaby
2020-02-09 13:26 ` Greg KH
2020-02-09 15:59 ` Sasha Levin [this message]
2020-02-09 17:02 ` Greg KH
2020-02-09 13:43 ` Martin Steigerwald
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=20200209155950.GD3584@sasha-vm \
--to=sashal@kernel.org \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=jslaby@suse.cz \
--cc=martin@lichtvoll.de \
--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