From: "tip-bot2 for Viresh Kumar" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Boqun Feng <boqun.feng@gmail.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: smp/core] smp: Fix typo in comment for raw_smp_processor_id()
Date: Fri, 13 Jun 2025 12:58:28 -0000 [thread overview]
Message-ID: <174981950839.406.6889829329461040913.tip-bot2@tip-bot2> (raw)
In-Reply-To: =?utf-8?q?=3Cd096779819962c305b85cd12bda41b593e0981aa=2E17495?= =?utf-8?q?36622=2Egit=2Eviresh=2Ekumar=40linaro=2Eorg=3E?=
The following commit has been merged into the smp/core branch of tip:
Commit-ID: 09735f0624b494c0959f3327af009283567af320
Gitweb: https://git.kernel.org/tip/09735f0624b494c0959f3327af009283567af320
Author: Viresh Kumar <viresh.kumar@linaro.org>
AuthorDate: Tue, 10 Jun 2025 13:27:13 +05:30
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Fri, 13 Jun 2025 14:48:54 +02:00
smp: Fix typo in comment for raw_smp_processor_id()
The comment in `smp.h` incorrectly refers to `raw_processor_id()`
instead of the correct function name `raw_smp_processor_id()`.
Suggested-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
Link: https://lore.kernel.org/all/d096779819962c305b85cd12bda41b593e0981aa.1749536622.git.viresh.kumar@linaro.org
---
include/linux/smp.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/smp.h b/include/linux/smp.h
index f1aa095..bea8d28 100644
--- a/include/linux/smp.h
+++ b/include/linux/smp.h
@@ -234,7 +234,7 @@ static inline int get_boot_cpu_id(void)
#endif /* !SMP */
/**
- * raw_processor_id() - get the current (unstable) CPU id
+ * raw_smp_processor_id() - get the current (unstable) CPU id
*
* For then you know what you are doing and need an unstable
* CPU id.
reply other threads:[~2025-06-13 12:58 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=174981950839.406.6889829329461040913.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.org \
--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®