From: xuanzhenggang001@208suo.com
To: ardb@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, dvhart@infradead.org,
andy@infradead.org
Subject: [PATCH] efi: x86: prefer 'unsigned int' to bare use of 'unsigned'
Date: Sun, 09 Jul 2023 10:20:18 +0800 [thread overview]
Message-ID: <d60c850cbfa5a25fcf97eef724f5b701@208suo.com> (raw)
In-Reply-To: <tencent_513E2ED35A17B9569C91CF75664724C7620A@qq.com>
This patch fixes the following checkpatch warning:
arch/x86/platform/efi/efi_64.c:109: WARNING: Prefer 'unsigned int' to
bare use of 'unsigned'
arch/x86/platform/efi/efi_64.c:177: WARNING: Prefer 'unsigned int' to
bare use of 'unsigned'
arch/x86/platform/efi/efi_64.c:182: WARNING: Prefer 'unsigned int' to
bare use of 'unsigned'
Signed-off-by: Zhenggang Xuan <xuanzhenggang001@208suo.com>
---
arch/x86/platform/efi/efi_64.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/platform/efi/efi_64.c
b/arch/x86/platform/efi/efi_64.c
index 232acf418cfb..0f69bd6eb144 100644
--- a/arch/x86/platform/efi/efi_64.c
+++ b/arch/x86/platform/efi/efi_64.c
@@ -106,7 +106,7 @@ int __init efi_alloc_page_tables(void)
*/
void efi_sync_low_kernel_mappings(void)
{
- unsigned num_entries;
+ unsigned int num_entries;
pgd_t *pgd_k, *pgd_efi;
p4d_t *p4d_k, *p4d_efi;
pud_t *pud_k, *pud_efi;
@@ -174,12 +174,12 @@ virt_to_phys_or_null_size(void *va, unsigned long
size)
#define virt_to_phys_or_null(addr) \
virt_to_phys_or_null_size((addr), sizeof(*(addr)))
-int __init efi_setup_page_tables(unsigned long pa_memmap, unsigned
num_pages)
+int __init efi_setup_page_tables(unsigned long pa_memmap, unsigned int
num_pages)
{
extern const u8 __efi64_thunk_ret_tramp[];
unsigned long pfn, text, pf, rodata, tramp;
struct page *page;
- unsigned npages;
+ unsigned int npages;
pgd_t *pgd = efi_mm.pgd;
/*
next parent reply other threads:[~2023-07-09 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_513E2ED35A17B9569C91CF75664724C7620A@qq.com>
2023-07-09 2:20 ` xuanzhenggang001 [this message]
2023-07-09 18:14 ` Andy Shevchenko
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=d60c850cbfa5a25fcf97eef724f5b701@208suo.com \
--to=xuanzhenggang001@208suo.com \
--cc=andy@infradead.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®