From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
bhelgaas@google.com, keescook@chromium.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] XArray: Fix xa_find_next for large multi-index entries" failed to apply to 5.4-stable tree
Date: Wed, 15 Apr 2020 18:49:49 -0400 [thread overview]
Message-ID: <20200415224949.GK1068@sasha-vm> (raw)
In-Reply-To: <20200415165122.GA3654762@kroah.com>
On Wed, Apr 15, 2020 at 06:51:22PM +0200, Greg KH wrote:
>On Wed, Apr 15, 2020 at 08:02:22AM -0700, Matthew Wilcox wrote:
>> On Wed, Apr 15, 2020 at 01:04:37PM +0200, gregkh@linuxfoundation.org wrote:
>> > The patch below does not apply to the 5.4-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 bd40b17ca49d7d110adf456e647701ce74de2241 Mon Sep 17 00:00:00 2001
>>
>> Seems like it's already there as commit
>> 16696ee7b58101c90bf21c3ab2443c57df4af24e
>
>Ugh.
>
>Sasha, your scripts are applying patches to older kernels before newer
>ones for some odd reason again, which confuses mine to no end :(
/me scratches head
It's in 5.6, 5.5, and 5.4. I've also queued them all at the same time
and you've released them all at the same time (Apr 8th).
Yes, it's tagged for stable, but I've grabbed it for the Fixes: tag.
What am I missing?
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-04-15 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 11:04 FAILED: patch "[PATCH] XArray: Fix xa_find_next for large multi-index entries" failed to apply to 5.4-stable tree gregkh
2020-04-15 15:02 ` Matthew Wilcox
2020-04-15 16:51 ` Greg KH
2020-04-15 22:49 ` Sasha Levin [this message]
2020-04-16 7:06 ` 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=20200415224949.GK1068@sasha-vm \
--to=sashal@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).