From: Koakuma via B4 Relay <devnull+koachan.protonmail.com@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, Koakuma <koachan@protonmail.com>
Subject: [PATCH 2/2] sparc/module: Make it clear that relocation numbers are shown in hex
Date: Mon, 09 Jun 2025 20:53:12 +0700 [thread overview]
Message-ID: <20250609-b4-sparc-relocs-v1-2-aa52631735af@protonmail.com> (raw)
In-Reply-To: <20250609-b4-sparc-relocs-v1-0-aa52631735af@protonmail.com>
From: Koakuma <koachan@protonmail.com>
This is to ease debugging by removing the ambiguity of the shown
number base.
Signed-off-by: Koakuma <koachan@protonmail.com>
---
arch/sparc/kernel/module.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/sparc/kernel/module.c b/arch/sparc/kernel/module.c
index 6e3d4dde4f9ab33040b300c40d5fd5d0584e166d..49740450a6859fda566459ee4679869f9854b760 100644
--- a/arch/sparc/kernel/module.c
+++ b/arch/sparc/kernel/module.c
@@ -142,7 +142,7 @@ int apply_relocate_add(Elf_Shdr *sechdrs,
break;
default:
- printk(KERN_ERR "module %s: Unknown relocation: %x\n",
+ printk(KERN_ERR "module %s: Unknown relocation: 0x%x\n",
me->name,
(int) (ELF_R_TYPE(rel[i].r_info) & 0xff));
return -ENOEXEC;
--
2.49.0
prev parent reply other threads:[~2025-06-09 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 13:53 [PATCH 0/2] sparc/module: R_SPARC_UA64 handling to help with LLVM IAS enablement Koakuma via B4 Relay
2025-06-09 13:53 ` [PATCH 1/2] sparc/module: Add R_SPARC_UA64 relocation handling Koakuma via B4 Relay
2025-08-03 1:15 ` Koakuma
2025-08-14 22:40 ` Nathan Chancellor
2025-08-15 9:30 ` Andreas Larsson
2025-08-18 16:17 ` Koakuma
2025-06-09 13:53 ` Koakuma via B4 Relay [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=20250609-b4-sparc-relocs-v1-2-aa52631735af@protonmail.com \
--to=devnull+koachan.protonmail.com@kernel.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=justinstitt@google.com \
--cc=koachan@protonmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=sparclinux@vger.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).