From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH] random: do not pretend to handle premature next security model
Date: Wed, 11 May 2022 12:32:19 +0200 [thread overview]
Message-ID: <YnuQlIOuOy7nHvSr@zx2c4.com> (raw)
In-Reply-To: <YntvKcp5PYDUKoFE@sol.localdomain>
Hi Eric,
On Wed, May 11, 2022 at 01:09:13AM -0700, Eric Biggers wrote:
> A couple very minor comments:
Thanks, will fix these.
Jason
next prev parent reply other threads:[~2022-05-11 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:30 [PATCH] random: do not pretend to handle premature next security model Jason A. Donenfeld
2022-05-11 8:09 ` Eric Biggers
2022-05-11 10:32 ` Jason A. Donenfeld [this message]
2022-05-15 0:45 ` Eric Biggers
2022-05-15 10:17 ` 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=YnuQlIOuOy7nHvSr@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.