From: Marek Vasut <marex@denx.de>
To: Dragan Simic <dsimic@manjaro.org>, Alex ThreeD <alexthreed@gmail.com>
Cc: u-boot@lists.denx.de, Ben Wolsieffer <benwolsieffer@gmail.com>,
Chris Morgan <macromorgan@hotmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Kever Yang <kever.yang@rock-chips.com>,
Philipp Tomsich <philipp.tomsich@theobroma-systems.com>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Quentin Schulz <quentin.schulz@cherry.de>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2] rockchip: board: Increase rng-seed size to make it sufficient for modern Linux
Date: Mon, 14 Oct 2024 22:12:51 +0200 [thread overview]
Message-ID: <ed98b4aa-da95-4ecd-bc89-bb827d799557@denx.de> (raw)
In-Reply-To: <839e5b9f561fa8e6328216618f9a2e38@manjaro.org>
On 10/14/24 9:28 PM, Dragan Simic wrote:
> On 2024-10-14 21:17, Alex ThreeD wrote:
>> On Mon, Oct 14, 2024 at 10:00 PM Dragan Simic <dsimic@manjaro.org> wrote:
>>> To sum up the replies from Marek, the lower limit should be 64.
>>
>> 64 by default, warning for custom values less than 32. Right?
>> Since 32 bytes is sufficient for kernels released in the last 2 years.
>
> I'd keep both the default and the warning threshold at 64. I think
> it's much safer that way.
Sounds good to me, thanks !
prev parent reply other threads:[~2024-10-14 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 17:53 [PATCH v2] rockchip: board: Increase rng-seed size to make it sufficient for modern Linux Alex Shumsky
2024-10-14 18:19 ` Dragan Simic
2024-10-14 18:50 ` Alex ThreeD
2024-10-14 19:00 ` Dragan Simic
2024-10-14 19:17 ` Alex ThreeD
2024-10-14 19:28 ` Dragan Simic
2024-10-14 20:12 ` Marek Vasut [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=ed98b4aa-da95-4ecd-bc89-bb827d799557@denx.de \
--to=marex@denx.de \
--cc=alexthreed@gmail.com \
--cc=benwolsieffer@gmail.com \
--cc=dsimic@manjaro.org \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=macromorgan@hotmail.com \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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