From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable 0/3] recent failed backports for the rng
Date: Thu, 13 Oct 2022 18:30:43 +0200 [thread overview]
Message-ID: <Y0g9M7Zr+1gbC6d5@kroah.com> (raw)
In-Reply-To: <Y0g6bYnxyNNX5WC6@kroah.com>
On Thu, Oct 13, 2022 at 06:18:53PM +0200, Greg KH wrote:
> On Thu, Oct 13, 2022 at 09:36:51AM -0600, Jason A. Donenfeld wrote:
> > Hi Greg,
> >
> > You just sent me an automated email about these failing, so here they
> > are backported.
>
> Backported where? Patch 1 is already in 5.10 and newer, does this one
> work in older?
>
> And 2 and 3 for all branches?
Ok, 2 and 3 are now queued up everywhere, only thing that didn't work is
patch 1 on the 4.9.y branch. Can you provide a working backport for
there?
thanks,
greg k-h
prev parent reply other threads:[~2022-10-13 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:36 [PATCH stable 0/3] recent failed backports for the rng Jason A. Donenfeld
2022-10-13 15:36 ` [PATCH stable 1/3] random: restore O_NONBLOCK support Jason A. Donenfeld
2022-10-13 16:20 ` Greg KH
2022-10-13 16:22 ` Greg KH
2022-10-13 16:32 ` [PATCH stable 4.9.y] " Jason A. Donenfeld
2022-10-13 17:02 ` Greg KH
2022-10-13 15:36 ` [PATCH stable 2/3] random: avoid reading two cache lines on irq randomness Jason A. Donenfeld
2022-10-13 15:36 ` [PATCH stable 3/3] random: use expired timer rather than wq for mixing fast pool Jason A. Donenfeld
2022-10-13 16:18 ` [PATCH stable 0/3] recent failed backports for the rng Greg KH
2022-10-13 16:29 ` Jason A. Donenfeld
2022-10-13 16:54 ` Greg KH
2022-10-13 17:01 ` Jason A. Donenfeld
2022-10-13 17:07 ` [PATCH stable 4.9.y 4.14.y] random: use expired timer rather than wq for mixing fast pool Jason A. Donenfeld
2022-10-13 17:17 ` Greg KH
2022-10-13 16:30 ` 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=Y0g9M7Zr+1gbC6d5@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