linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baokun Li <libaokun1@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
	<x86@kernel.org>, <hpa@zytor.com>, <jroedel@suse.de>,
	<trix@redhat.com>, <brijesh.singh@amd.com>, <rostedt@goodmis.org>,
	<ying-tsun.huang@amd.com>, <linux-kernel@vger.kernel.org>
Cc: <weiyongjun1@huawei.com>, <yuehaibing@huawei.com>,
	<yangjihong1@huawei.com>, <yukuai3@huawei.com>,
	<libaokun1@huawei.com>
Subject: [PATCH -next] x86/mm/mtrr: fix doc warnings in generic.c
Date: Sat, 5 Jun 2021 14:48:21 +0800	[thread overview]
Message-ID: <20210605064821.694432-1-libaokun1@huawei.com> (raw)

Fixes the following W=1 kernel build warning(s):

 arch/x86/kernel/cpu/mtrr/generic.c:120: warning: Function parameter or 
  member 'start' not described in 'mtrr_type_lookup_fixed'
 arch/x86/kernel/cpu/mtrr/generic.c:120: warning: Function parameter or 
  member 'end' not described in 'mtrr_type_lookup_fixed'
 arch/x86/kernel/cpu/mtrr/generic.c:161: warning: Function parameter or 
  member 'start' not described in 'mtrr_type_lookup_variable'
 arch/x86/kernel/cpu/mtrr/generic.c:161: warning: Function parameter or 
  member 'end' not described in 'mtrr_type_lookup_variable'
 arch/x86/kernel/cpu/mtrr/generic.c:161: warning: Function parameter or 
  member 'partial_end' not described in 'mtrr_type_lookup_variable'
 arch/x86/kernel/cpu/mtrr/generic.c:161: warning: Function parameter or 
  member 'repeat' not described in 'mtrr_type_lookup_variable'
 arch/x86/kernel/cpu/mtrr/generic.c:161: warning: Function parameter or 
  member 'uniform' not described in 'mtrr_type_lookup_variable'
 arch/x86/kernel/cpu/mtrr/generic.c:255: warning: Function parameter or 
  member 'start' not described in 'mtrr_type_lookup'
 arch/x86/kernel/cpu/mtrr/generic.c:255: warning: Function parameter or 
  member 'end' not described in 'mtrr_type_lookup'
 arch/x86/kernel/cpu/mtrr/generic.c:255: warning: Function parameter or 
  member 'uniform' not described in 'mtrr_type_lookup'

Signed-off-by: Baokun Li <libaokun1@huawei.com>
---
 arch/x86/kernel/cpu/mtrr/generic.c | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/arch/x86/kernel/cpu/mtrr/generic.c b/arch/x86/kernel/cpu/mtrr/generic.c
index 558108296f3c..8a943a83845e 100644
--- a/arch/x86/kernel/cpu/mtrr/generic.c
+++ b/arch/x86/kernel/cpu/mtrr/generic.c
@@ -104,7 +104,8 @@ static int check_type_overlap(u8 *prev, u8 *curr)
 
 /**
  * mtrr_type_lookup_fixed - look up memory type in MTRR fixed entries
- *
+ * @start: Start addaress.
+ * @end: End address.
  * Return the MTRR fixed memory type of 'start'.
  *
  * MTRR fixed entries are divided into the following ways:
@@ -143,7 +144,11 @@ static u8 mtrr_type_lookup_fixed(u64 start, u64 end)
 
 /**
  * mtrr_type_lookup_variable - look up memory type in MTRR variable entries
- *
+ * @start: Start addaress.
+ * @end: End address.
+ * @partial_end: Partial end address.
+ * @repeat: Memory is repeat or not.
+ * @uniform: Memory is uniform or not.
  * Return Value:
  * MTRR_TYPE_(type) - Matched memory type or default memory type (unmatched)
  *
@@ -241,7 +246,9 @@ static u8 mtrr_type_lookup_variable(u64 start, u64 end, u64 *partial_end,
 
 /**
  * mtrr_type_lookup - look up memory type in MTRR
- *
+ * @start: Start addaress.
+ * @end: End address.
+ * @uniform: Memory is uniform or not.
  * Return Values:
  * MTRR_TYPE_(type)  - The effective MTRR type for the region
  * MTRR_TYPE_INVALID - MTRR is disabled
-- 
2.31.1


             reply	other threads:[~2021-06-05  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-05  6:48 Baokun Li [this message]
2021-06-10  7:35 ` [PATCH -next] x86/mm/mtrr: fix doc warnings in generic.c Borislav Petkov

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=20210605064821.694432-1-libaokun1@huawei.com \
    --to=libaokun1@huawei.com \
    --cc=bp@alien8.de \
    --cc=brijesh.singh@amd.com \
    --cc=hpa@zytor.com \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=trix@redhat.com \
    --cc=weiyongjun1@huawei.com \
    --cc=x86@kernel.org \
    --cc=yangjihong1@huawei.com \
    --cc=ying-tsun.huang@amd.com \
    --cc=yuehaibing@huawei.com \
    --cc=yukuai3@huawei.com \
    /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).