From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable 5.10 5.15 5.17 5.18] Revert "random: use static branch for crng_ready()"
Date: Tue, 7 Jun 2022 11:14:35 +0200 [thread overview]
Message-ID: <Yp8W+zkF2QUngWG0@kroah.com> (raw)
In-Reply-To: <20220607084005.666059-1-Jason@zx2c4.com>
On Tue, Jun 07, 2022 at 10:40:05AM +0200, Jason A. Donenfeld wrote:
> This reverts upstream commit f5bda35fba615ace70a656d4700423fa6c9bebee
> from stable. It's not essential and will take some time during 5.19 to
> work out properly.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> drivers/char/random.c | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-06-07 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 8:40 [PATCH stable 5.10 5.15 5.17 5.18] Revert "random: use static branch for crng_ready()" Jason A. Donenfeld
2022-06-07 9:14 ` 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=Yp8W+zkF2QUngWG0@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 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).