From: trix@redhat.com
To: dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, Tom Rix <trix@redhat.com>
Subject: [PATCH] mm: remove h from printk format specifier
Date: Tue, 15 Dec 2020 06:19:31 -0800 [thread overview]
Message-ID: <20201215141931.1842379-1-trix@redhat.com> (raw)
From: Tom Rix <trix@redhat.com>
See Documentation/core-api/printk-formats.rst.
h should no longer be used in the format specifier for printk.
Signed-off-by: Tom Rix <trix@redhat.com>
---
arch/x86/mm/fault.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index 907b54d3b990..4bc4c9a6a8ae 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -486,13 +486,13 @@ static void show_ldttss(const struct desc_ptr *gdt, const char *name, u16 index)
}
if (offset + sizeof(struct ldttss_desc) >= gdt->size) {
- pr_alert("%s: 0x%hx -- out of bounds\n", name, index);
+ pr_alert("%s: 0x%x -- out of bounds\n", name, index);
return;
}
if (copy_from_kernel_nofault(&desc, (void *)(gdt->address + offset),
sizeof(struct ldttss_desc))) {
- pr_alert("%s: 0x%hx -- GDT entry is not readable\n",
+ pr_alert("%s: 0x%x -- GDT entry is not readable\n",
name, index);
return;
}
@@ -501,7 +501,7 @@ static void show_ldttss(const struct desc_ptr *gdt, const char *name, u16 index)
#ifdef CONFIG_X86_64
addr |= ((u64)desc.base3 << 32);
#endif
- pr_alert("%s: 0x%hx -- base=0x%lx limit=0x%x\n",
+ pr_alert("%s: 0x%x -- base=0x%lx limit=0x%x\n",
name, index, addr, (desc.limit0 | (desc.limit1 << 16)));
}
@@ -569,7 +569,7 @@ show_fault_oops(struct pt_regs *regs, unsigned long error_code, unsigned long ad
/* Usable even on Xen PV -- it's just slow. */
native_store_gdt(&gdt);
- pr_alert("IDT: 0x%lx (limit=0x%hx) GDT: 0x%lx (limit=0x%hx)\n",
+ pr_alert("IDT: 0x%lx (limit=0x%x) GDT: 0x%lx (limit=0x%x)\n",
idt.address, idt.size, gdt.address, gdt.size);
store_ldt(ldtr);
--
2.27.0
next reply other threads:[~2020-12-15 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 14:19 trix [this message]
2020-12-15 15:02 ` Peter Zijlstra
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=20201215141931.1842379-1-trix@redhat.com \
--to=trix@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®