From: Baokun Li <libaokun1@huawei.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<x86@kernel.org>, <hpa@zytor.com>, <feng.tang@intel.com>,
<luming.yu@intel.com>, <paulmck@kernel.org>,
<peterz@infradead.org>, <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/tsc: fix doc warnings in tsc.c
Date: Thu, 10 Jun 2021 19:42:01 +0800 [thread overview]
Message-ID: <20210610114201.3440584-1-libaokun1@huawei.com> (raw)
Fixes the following W=1 kernel build warning(s):
arch/x86/kernel/tsc.c:1275: warning: Excess function
parameter 'cycles' description in 'convert_art_ns_to_tsc'
arch/x86/kernel/tsc.c:1275: warning: Excess function
parameter 'cs' description in 'convert_art_ns_to_tsc'
arch/x86/kernel/tsc.c:1309: warning: Function parameter or
member 'work' not described in 'tsc_refine_calibration_work'
Signed-off-by: Baokun Li <libaokun1@huawei.com>
---
arch/x86/kernel/tsc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
index 2e076a459a0c..312591c8e3d6 100644
--- a/arch/x86/kernel/tsc.c
+++ b/arch/x86/kernel/tsc.c
@@ -1265,8 +1265,8 @@ EXPORT_SYMBOL(convert_art_to_tsc);
* Return:
* struct system_counterval_t - system counter value with the pointer to the
* corresponding clocksource
- * @cycles: System counter value
- * @cs: Clocksource corresponding to system counter value. Used
+ * cycles: System counter value
+ * cs: Clocksource corresponding to system counter value. Used
* by timekeeping code to verify comparability of two cycle
* values.
*/
@@ -1293,7 +1293,7 @@ static void tsc_refine_calibration_work(struct work_struct *work);
static DECLARE_DELAYED_WORK(tsc_irqwork, tsc_refine_calibration_work);
/**
* tsc_refine_calibration_work - Further refine tsc freq calibration
- * @work - ignored.
+ * @work: ignored.
*
* This functions uses delayed work over a period of a
* second to further refine the TSC freq value. Since this is
--
2.31.1
reply other threads:[~2021-06-10 11:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210610114201.3440584-1-libaokun1@huawei.com \
--to=libaokun1@huawei.com \
--cc=bp@alien8.de \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=weiyongjun1@huawei.com \
--cc=x86@kernel.org \
--cc=yangjihong1@huawei.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).