From: "tip-bot2 for Paul Menzel" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Ard Biesheuvel <ardb@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: efi/core] x86/efi: Log 32/64-bit mismatch with kernel as an error
Date: Sun, 23 May 2021 10:04:46 -0000 [thread overview]
Message-ID: <162176428679.29796.2511069274477726490.tip-bot2@tip-bot2> (raw)
The following commit has been merged into the efi/core branch of tip:
Commit-ID: bb11580f61b6c4ba5c35706abd927c8ac8c32852
Gitweb: https://git.kernel.org/tip/bb11580f61b6c4ba5c35706abd927c8ac8c32852
Author: Paul Menzel <pmenzel@molgen.mpg.de>
AuthorDate: Sat, 15 May 2021 10:14:04 +02:00
Committer: Ard Biesheuvel <ardb@kernel.org>
CommitterDate: Sat, 22 May 2021 14:09:07 +02:00
x86/efi: Log 32/64-bit mismatch with kernel as an error
Log the message
No EFI runtime due to 32/64-bit mismatch with kernel
as an error condition, as several things like efivarfs won’t work
without the EFI runtime.
Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
---
arch/x86/platform/efi/efi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/platform/efi/efi.c b/arch/x86/platform/efi/efi.c
index 8a26e70..147c30a 100644
--- a/arch/x86/platform/efi/efi.c
+++ b/arch/x86/platform/efi/efi.c
@@ -468,7 +468,7 @@ void __init efi_init(void)
*/
if (!efi_runtime_supported())
- pr_info("No EFI runtime due to 32/64-bit mismatch with kernel\n");
+ pr_err("No EFI runtime due to 32/64-bit mismatch with kernel\n");
if (!efi_runtime_supported() || efi_runtime_disabled()) {
efi_memmap_unmap();
reply other threads:[~2021-05-23 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=162176428679.29796.2511069274477726490.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=x86@kernel.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).