From: Phil Elwell <phil@raspberrypi.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
linux@armlinux.org.uk, rmk+kernel@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com
Cc: Stephen Boyd <swboyd@chromium.org>,
Ard Biesheuvel <ardb@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] ARM: initialize jump labels before setup_machine_fdt()
Date: Tue, 7 Jun 2022 09:29:09 +0100 [thread overview]
Message-ID: <8cc7ebe4-442b-a24b-9bb0-fce6e0425ee6@raspberrypi.com> (raw)
This patch is fatal for me in the downstream Raspberry Pi kernel - it locks up
on boot even before the earlycon output is available. Hacking jump_label_init to
skip the jump_entry for "crng_is_ready" allows it to boot, but is likely to have
consequences further down the line.
The stable branch may not be living up to its name, but I don't think this is a
quick fix.
Phil
next reply other threads:[~2022-06-07 8:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 8:29 Phil Elwell [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=8cc7ebe4-442b-a24b-9bb0-fce6e0425ee6@raspberrypi.com \
--to=phil@raspberrypi.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).