From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v2] m68k: virt: pass RNG seed via bootinfo block
Date: Wed, 6 Jul 2022 11:05:44 +0200 [thread overview]
Message-ID: <CAMuHMdXZ28mSeycCXMMtHchPNPY+yRC_=ysN4aTdA8OOJtHyXQ@mail.gmail.com> (raw)
In-Reply-To: <20220626111804.330745-1-Jason@zx2c4.com>
On Sun, Jun 26, 2022 at 1:18 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> This commit wires up bootinfo's RNG seed attribute so that Linux VMs can
> have their RNG seeded from the earliest possible time in boot, just like
> the "rng-seed" device tree property on those platforms. The link
> contains the corresponding Linux patch.
>
> Link: https://lore.kernel.org/lkml/20220626111509.330159-1-Jason@zx2c4.com/
> Based-on: <20220625152318.120849-1-Jason@zx2c4.com>
> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-07-06 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 15:44 [PATCH qemu] m68k: virt: pass RNG seed via bootinfo block Jason A. Donenfeld
2022-06-25 16:34 ` Laurent Vivier
2022-06-26 11:18 ` [PATCH v2] " Jason A. Donenfeld
2022-07-06 9:05 ` Geert Uytterhoeven [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='CAMuHMdXZ28mSeycCXMMtHchPNPY+yRC_=ysN4aTdA8OOJtHyXQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=Jason@zx2c4.com \
--cc=laurent@vivier.eu \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.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).