From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Phil Elwell <phil@raspberrypi.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Russell King <rmk+kernel@armlinux.org.uk>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Stephen Boyd <swboyd@chromium.org>,
Ard Biesheuvel <ardb@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: initialize jump labels before setup_machine_fdt()
Date: Tue, 7 Jun 2022 13:09:03 +0200 [thread overview]
Message-ID: <Yp8xz0gfsRKgSO/n@zx2c4.com> (raw)
In-Reply-To: <c47c42e3-1d56-5859-a6ad-976a1a3381c6@raspberrypi.com>
Hi Phil,
On Tue, Jun 07, 2022 at 12:04:13PM +0100, Phil Elwell wrote:
> A clean 5.15.45 boots cleanly, whereas a downstream kernel shows the static key
> warning (but it does go on to boot). The significant difference is that our
> defconfigs set CONFIG_RANDOM_TRUST_BOOTLOADER=y - defining that on top of
> multi_v7_defconfig demonstrates the issue on a clean 5.15.45. Conversely, not
> setting that option in a downstream kernel build avoids the warning
Ah, that makes sense. Note that I've got a patch out for changing that
defconfig as well to be Y, which means the CI will catch this sort of
thing in the future.
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-07 11:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8cc7ebe4-442b-a24b-9bb0-fce6e0425ee6@raspberrypi.com>
2022-06-07 8:30 ` [PATCH v2] ARM: initialize jump labels before setup_machine_fdt() Jason A. Donenfeld
2022-06-07 8:47 ` Phil Elwell
2022-06-07 8:51 ` Jason A. Donenfeld
2022-06-07 10:06 ` Catalin Marinas
2022-06-07 10:11 ` Jason A. Donenfeld
2022-06-08 8:20 ` Jason A. Donenfeld
2022-06-08 9:16 ` Catalin Marinas
2022-06-07 9:10 ` Greg KH
2022-06-07 11:04 ` Phil Elwell
2022-06-07 11:09 ` Jason A. Donenfeld [this message]
2022-06-07 9:14 ` Russell King (Oracle)
2022-06-07 9:16 ` Jason A. Donenfeld
2022-06-07 8:43 ` Jason A. Donenfeld
2022-06-07 9:15 ` Phil Elwell
2022-06-07 15:14 ` Jason A. Donenfeld
2022-06-07 15:35 ` Phil Elwell
2022-06-07 15:44 ` Jason A. Donenfeld
2022-06-07 15:51 ` Phil Elwell
2022-06-07 19:30 ` [PATCH v3] " Jason A. Donenfeld
2022-06-08 8:18 ` Jason A. Donenfeld
2022-06-03 12:15 [PATCH v2] " 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=Yp8xz0gfsRKgSO/n@zx2c4.com \
--to=jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=phil@raspberrypi.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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