From: Simon Horman <horms@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: horms@kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, kexec@lists.infradead.org
Subject: Re: [PATCH kexec-tools v3] m68k: pass rng seed via BI_RNG_SEED
Date: Fri, 18 Nov 2022 16:15:52 +0100 [thread overview]
Message-ID: <Y3ehqF20MWK1B+gO@vergenet.net> (raw)
In-Reply-To: <20221114154303.1176987-1-Jason@zx2c4.com>
On Mon, Nov 14, 2022 at 04:43:03PM +0100, Jason A. Donenfeld wrote:
> In order to pass fresh entropy to kexec'd kernels, use BI_RNG_SEED
> for passing a seed, with the same semantics that kexec-tools currently
> uses for i386's setup_data.
>
> Link: https://git.kernel.org/torvalds/c/dc63a086daee92c63e3
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Thanks Jason,
applied.
prev parent reply other threads:[~2022-11-18 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 1:35 [PATCH v2 RESEND kexec-tools] m68k: pass rng seed via BI_RNG_SEED Jason A. Donenfeld
2022-11-14 15:31 ` Simon Horman
2022-11-14 15:39 ` Jason A. Donenfeld
2022-11-14 15:43 ` [PATCH kexec-tools v3] " Jason A. Donenfeld
2022-11-18 15:15 ` Simon Horman [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=Y3ehqF20MWK1B+gO@vergenet.net \
--to=horms@kernel.org \
--cc=Jason@zx2c4.com \
--cc=geert@linux-m68k.org \
--cc=kexec@lists.infradead.org \
--cc=linux-m68k@lists.linux-m68k.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