From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Helge Deller <deller@gmx.de>,
geert@linux-m68k.org, svens@stackframe.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] Revert "fbcon: Disable accelerated scrolling"" failed to apply to 5.10-stable tree
Date: Sun, 6 Feb 2022 14:10:45 +0100 [thread overview]
Message-ID: <Yf/I1S+hXA8aJ3B5@kroah.com> (raw)
In-Reply-To: <CAKMK7uFB--nvHStJLPLFMDh_+4+Xt6fSCQVt5YO29K2uReQ5Tw@mail.gmail.com>
On Sun, Feb 06, 2022 at 01:55:35PM +0100, Daniel Vetter wrote:
> On Sat, Feb 5, 2022 at 7:36 PM Helge Deller <deller@gmx.de> wrote:
> >
> > * gregkh@linuxfoundation.org <gregkh@linuxfoundation.org>:
> > >
> > > The patch below does not apply to the 5.10-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>.
> >
> > Hello Greg,
> >
> > below is a rebased patch which you can use instead and which applies cleanly.
> > The attached patch below is a 100% "git revert 397971e1d891", with added
> > info to the commit message.
> >
> > After applying the patch below, the other failed patch:
> > "[PATCH] fbcon: Add option to enable legacy hardware acceleration"
> > doesn't fail to apply any longer either.
> >
> > Please make sure to apply BOTH patches (the one below and the other
> > failed one) or NONE of those two patches.
> >
> > Ideally, I'd suggest to wait until monday to get an Ack from Daniel for this.
>
> Ack.
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-02-06 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 13:12 FAILED: patch "[PATCH] Revert "fbcon: Disable accelerated scrolling"" failed to apply to 5.10-stable tree gregkh
2022-02-05 18:36 ` Helge Deller
2022-02-06 12:55 ` Daniel Vetter
2022-02-06 13:10 ` Greg KH [this message]
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=Yf/I1S+hXA8aJ3B5@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=stable@vger.kernel.org \
--cc=svens@stackframe.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