All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: stable <stable@vger.kernel.org>
Subject: Re: [PATCH stable 5.10 5.15 5.17 5.18] arm64: Initialize jump labels before setup_machine_fdt()
Date: Tue, 7 Jun 2022 12:05:40 +0200	[thread overview]
Message-ID: <Yp8i9DH57dRGfTNf@kroah.com> (raw)
In-Reply-To: <CAHmME9pkWz_DBww8YOTzKtbxbjRgNkjDTRfxy2Hr-pur0dVA0A@mail.gmail.com>

On Tue, Jun 07, 2022 at 11:51:23AM +0200, Jason A. Donenfeld wrote:
> On Tue, Jun 7, 2022 at 11:49 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Jun 07, 2022 at 10:56:21AM +0200, Jason A. Donenfeld wrote:
> > > You can actually drop this in favor of
> > > https://lore.kernel.org/stable/20220607084005.666059-1-Jason@zx2c4.com/
> > > rather than playing whack-a-mole by architectures that may have been
> > > broken by it.
> >
> > So I need to drop this as well?  Or is it ok to keep for now now that I
> > have queued up the other commit?
> 
> The other commit ("Revert "random: use static branch for
> crng_ready()"") fixes this problem on all architectures. This commit
> fixes the problem on arm64. There's probably no harm in keeping this
> commit, if you want it, but it's also no longer necessary, because
> "Revert "random: use static branch for crng_ready()"" addresses the
> issue more comprehensively.

I'll just leave this as-is for now, that's simpler.

thanks,

greg k-h

      reply	other threads:[~2022-06-07 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04  6:25 [PATCH stable 5.10 5.15 5.17 5.18] arm64: Initialize jump labels before setup_machine_fdt() Jason A. Donenfeld
2022-06-06  6:54 ` Greg KH
2022-06-07  8:56   ` Jason A. Donenfeld
2022-06-07  9:49     ` Greg KH
2022-06-07  9:51       ` Jason A. Donenfeld
2022-06-07 10:05         ` 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=Yp8i9DH57dRGfTNf@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.