From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: keescook@chromium.org, pageexec@freemail.hu, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] gcc-plugins: latent_entropy: use /dev/urandom" failed to apply to 4.9-stable tree
Date: Mon, 18 Apr 2022 11:39:52 +0200 [thread overview]
Message-ID: <Yl0x6HEAlUdeu/Mi@zx2c4.com> (raw)
In-Reply-To: <Yl0vnls++OCbpGzX@kroah.com>
Hi Greg,
On Mon, Apr 18, 2022 at 11:30:06AM +0200, Greg KH wrote:
> On Mon, Apr 18, 2022 at 11:12:11AM +0200, Jason A. Donenfeld wrote:
> > Hi Greg,
> >
> > On Mon, Apr 18, 2022 at 10:10:45AM +0200, gregkh@linuxfoundation.org wrote:
> > >
> > > The patch below does not apply to the 4.9-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 c40160f2998c897231f8454bf797558d30a20375 Mon Sep 17 00:00:00 2001
> >
> > Apparently on 4.9.y, applying this commit cleanly also requires
> > 5a45a4c5c3f5e36a03770deb102ca6ba256ff3d7 to be cherry picked first.
>
> That worked, thanks!
Hold up a second; that won't actually compile. Sorry about that, I'm
doing this all on my phone and a bit slow.
I'll do a standalone backport of c40160f without 5a45a4, and will mail
it out shortly.
Jason
prev parent reply other threads:[~2022-04-18 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 8:10 FAILED: patch "[PATCH] gcc-plugins: latent_entropy: use /dev/urandom" failed to apply to 4.9-stable tree gregkh
2022-04-18 9:12 ` Jason A. Donenfeld
2022-04-18 9:30 ` Greg KH
2022-04-18 9:39 ` Jason A. Donenfeld [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=Yl0x6HEAlUdeu/Mi@zx2c4.com \
--to=jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=pageexec@freemail.hu \
--cc=stable@vger.kernel.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