From: "tip-bot2 for Baokun Li" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Baokun Li <libaokun1@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: smp/core] cpu/hotplug: Fix kernel doc warnings for __cpuhp_setup_state_cpuslocked()
Date: Tue, 10 Aug 2021 16:14:40 -0000 [thread overview]
Message-ID: <162861208037.395.5262831120311169946.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20210605063003.681049-1-libaokun1@huawei.com>
The following commit has been merged into the smp/core branch of tip:
Commit-ID: ed3cd1da674034c4800abfc48c26f2742d5df17e
Gitweb: https://git.kernel.org/tip/ed3cd1da674034c4800abfc48c26f2742d5df17e
Author: Baokun Li <libaokun1@huawei.com>
AuthorDate: Sat, 05 Jun 2021 14:30:03 +08:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Tue, 10 Aug 2021 18:07:38 +02:00
cpu/hotplug: Fix kernel doc warnings for __cpuhp_setup_state_cpuslocked()
Fixes the following W=1 kernel build warning(s):
kernel/cpu.c:1949: warning: Function parameter or member
'name' not described in '__cpuhp_setup_state_cpuslocked'
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210605063003.681049-1-libaokun1@huawei.com
---
kernel/cpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/cpu.c b/kernel/cpu.c
index 804b847..8930a4e 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -1976,6 +1976,7 @@ EXPORT_SYMBOL_GPL(__cpuhp_state_add_instance);
/**
* __cpuhp_setup_state_cpuslocked - Setup the callbacks for an hotplug machine state
* @state: The state to setup
+ * @name: Name of the step
* @invoke: If true, the startup function is invoked for cpus where
* cpu state >= @state
* @startup: startup callback function
prev parent reply other threads:[~2021-08-10 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 6:30 [PATCH -next] cpu/hotplug: fix doc warnings in cpu.c Baokun Li
2021-08-10 16:14 ` tip-bot2 for Baokun Li [this message]
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=162861208037.395.5262831120311169946.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=libaokun1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.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®