From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
ebiggers@google.com, tytso@mit.edu,
torvalds@linux-foundation.org
Subject: Re: [PATCH] random: cap jitter samples per bit to factor of HZ
Date: Wed, 13 Jul 2022 18:21:48 +0200 [thread overview]
Message-ID: <Ys7xHMIF6OLkLbvv@zx2c4.com> (raw)
In-Reply-To: <88d9e600-b687-7d09-53cb-727601612e21@arm.com>
Hi Vladmir,
On Wed, Jul 13, 2022 at 04:52:20PM +0100, Vladimir Murzin wrote:
> On 7/13/22 16:11, Jason A. Donenfeld wrote:
> > Vladimir - Can you let me know if this appears to fix the issue you're
> > seeing? -Jason
>
> Works for me, thanks! :)
> Tested-by: Vladimir Murzin <vladimir.murzin@arm.com>
Thanks for testing. I'll push this out to Linus probably tomorrow.
(Though I noticed that Linus is in the CC for this thread already, and
he's been on a patch picking spree as of late, so in case he happens to
be following along, fell free to pick away. Otherwise I'll send a pull
not before long.)
Jason
next prev parent reply other threads:[~2022-07-13 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:20 [PATCH] random: vary jitter iterations based on cycle counter speed Jason A. Donenfeld
2022-07-13 14:31 ` Vladimir Murzin
2022-07-13 14:40 ` Jason A. Donenfeld
2022-07-13 14:52 ` Vladimir Murzin
2022-07-13 14:53 ` Jason A. Donenfeld
2022-07-13 15:11 ` [PATCH] random: cap jitter samples per bit to factor of HZ Jason A. Donenfeld
2022-07-13 15:52 ` Vladimir Murzin
2022-07-13 16:21 ` Jason A. Donenfeld [this message]
2022-07-16 17:45 ` Linus Torvalds
2022-07-16 18:09 ` Jason A. Donenfeld
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=Ys7xHMIF6OLkLbvv@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ebiggers@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vladimir.murzin@arm.com \
/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