From: Qiang Ma <maqianga@uniontech.com>
To: ardb@kernel.org, linux@armlinux.org.uk
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Qiang Ma <maqianga@uniontech.com>
Subject: [PATCH 2/2] efi/arm*: Remove the useless failure return message print
Date: Thu, 23 Oct 2025 16:21:29 +0800 [thread overview]
Message-ID: <20251023082129.75612-2-maqianga@uniontech.com> (raw)
In-Reply-To: <20251023082129.75612-1-maqianga@uniontech.com>
In the efi_create_mapping() in arch/arm*/kernel/efi.c,
the return value is always 0, and this debug message
is unnecessary. So, remove it.
Signed-off-by: Qiang Ma <maqianga@uniontech.com>
---
drivers/firmware/efi/arm-runtime.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/firmware/efi/arm-runtime.c b/drivers/firmware/efi/arm-runtime.c
index 83092d93f36a..ca27fbfaff5c 100644
--- a/drivers/firmware/efi/arm-runtime.c
+++ b/drivers/firmware/efi/arm-runtime.c
@@ -66,12 +66,7 @@ static bool __init efi_virtmap_init(void)
if (md->virt_addr == U64_MAX)
return false;
- ret = efi_create_mapping(&efi_mm, md);
- if (ret) {
- pr_warn(" EFI remap %pa: failed to create mapping (%d)\n",
- &phys, ret);
- return false;
- }
+ efi_create_mapping(&efi_mm, md);
}
if (efi_memattr_apply_permissions(&efi_mm, efi_set_mapping_permissions))
--
2.20.1
next prev parent reply other threads:[~2025-10-23 8:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 8:21 [PATCH 1/2] ARM/efi: Remove duplicate permission settings Qiang Ma
2025-10-23 8:21 ` Qiang Ma [this message]
2025-10-24 2:00 ` [PATCH 2/2] efi/arm*: Remove the useless failure return message print kernel test robot
2025-10-23 8:30 ` [PATCH 1/2] ARM/efi: Remove duplicate permission settings Ard Biesheuvel
2025-10-27 3:45 ` Qiang Ma
2025-10-28 13:42 ` Ard Biesheuvel
2025-10-29 9:54 ` Qiang Ma
2025-10-29 14:15 ` Ard Biesheuvel
2025-10-30 7:36 ` Qiang Ma
2025-10-30 10:02 ` Ard Biesheuvel
2025-10-30 10:24 ` Qiang Ma
2025-10-30 10:36 ` Ard Biesheuvel
2025-10-30 10:44 ` Qiang Ma
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=20251023082129.75612-2-maqianga@uniontech.com \
--to=maqianga@uniontech.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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