From: Kael D'Alcamo <dev@kael-k.io>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] x86/cpu: Fix kernel-doc warnings
Date: Sun, 5 Oct 2025 22:41:19 +0200 [thread overview]
Message-ID: <20251005204200.191346-1-dev@kael-k.io> (raw)
Fix the following kernel-doc warnings found by `make W=1`:
Warning: arch/x86/kernel/cpu/mtrr/amd.c:60 function parameter 'reg' not described in 'amd_set_mtrr'
Warning: arch/x86/kernel/cpu/mtrr/amd.c:60 function parameter 'base' not described in 'amd_set_mtrr'
Warning: arch/x86/kernel/cpu/mtrr/amd.c:60 function parameter 'size' not described in 'amd_set_mtrr'
Warning: arch/x86/kernel/cpu/mtrr/amd.c:60 function parameter 'type' not described in 'amd_set_mtrr'
Warning: arch/x86/kernel/cpu/mtrr/centaur.c:27 function parameter 'replace_reg' not described in 'centaur_get_free_region'
Kael D'Alcamo (2):
x86/cpu: Fix kernel-doc for 'amd_set_mtrr'
x86/cpu: Fix kernel-doc for 'centaur_get_free_region'
arch/x86/kernel/cpu/mtrr/amd.c | 8 ++++----
arch/x86/kernel/cpu/mtrr/centaur.c | 1 +
2 files changed, 5 insertions(+), 4 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-05 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 20:41 Kael D'Alcamo [this message]
2025-10-05 20:41 ` [PATCH 1/2] x86/cpu: Fix kernel-doc for 'amd_set_mtrr' Kael D'Alcamo
2025-10-05 20:41 ` [PATCH 2/2] x86/cpu: Fix kernel-doc for 'centaur_get_free_region' Kael D'Alcamo
2025-10-21 10:37 ` Borislav Petkov
2025-10-26 19:54 ` [PATCH v2 0/1] x86/mtrr: Fix kernel-doc warnings in amd.c and centaur.c Kael D'Alcamo
2025-10-26 19:54 ` [PATCH v2 1/1] " Kael D'Alcamo
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=20251005204200.191346-1-dev@kael-k.io \
--to=dev@kael-k.io \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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®