From: Laurent Vivier <laurent@vivier.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux-m68k@lists.linux-m68k.org, qemu-devel@nongnu.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH qemu v2 1/2] m68k: rework BI_VIRT_RNG_SEED as BI_RNG_SEED
Date: Thu, 29 Sep 2022 08:37:24 +0200 [thread overview]
Message-ID: <17166083-0941-7644-9bfe-a57203b69fdd@vivier.eu> (raw)
In-Reply-To: <20220926113900.1256630-1-Jason@zx2c4.com>
Le 26/09/2022 à 13:38, Jason A. Donenfeld a écrit :
> Following a change on the kernel side (see link), pass BI_RNG_SEED
> instead of BI_VIRT_RNG_SEED. This should have no impact on
> compatibility, as there will simply be no effect if it's an old kernel,
> which is how things have always been. We then use this as an opportunity
> to add this to q800, since now we can, which is a nice improvement.
>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Laurent Vivier <laurent@vivier.eu>
> Link: https://lore.kernel.org/lkml/20220923170340.4099226-3-Jason@zx2c4.com/
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> hw/m68k/q800.c | 7 +++++++
> hw/m68k/virt.c | 2 +-
> include/standard-headers/asm-m68k/bootinfo-virt.h | 4 +++-
> include/standard-headers/asm-m68k/bootinfo.h | 8 +++++++-
> 4 files changed, 18 insertions(+), 3 deletions(-)
>
Applied to my m68k-for-7.2 branch
Thanks,
Laurent
prev parent reply other threads:[~2022-09-29 6:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 11:38 [PATCH qemu v2 1/2] m68k: rework BI_VIRT_RNG_SEED as BI_RNG_SEED Jason A. Donenfeld
2022-09-26 11:39 ` [PATCH qemu v2 2/2] m68k: align bootinfo strings and data to 4 bytes Jason A. Donenfeld
2022-09-26 13:00 ` Laurent Vivier
2022-09-26 21:37 ` Laurent Vivier
2022-09-26 21:40 ` Jason A. Donenfeld
2022-09-26 21:42 ` Laurent Vivier
2022-09-26 21:42 ` Jason A. Donenfeld
2022-09-28 23:13 ` Jason A. Donenfeld
2022-09-29 6:37 ` Laurent Vivier [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=17166083-0941-7644-9bfe-a57203b69fdd@vivier.eu \
--to=laurent@vivier.eu \
--cc=Jason@zx2c4.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--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).