From: Miguel Ojeda <ojeda@kernel.org>
To: John Stultz <jstultz@google.com>, Thomas Gleixner <tglx@linutronix.de>
Cc: Stephen Boyd <sboyd@kernel.org>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Ingo Molnar <mingo@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Nicholas Mc Guire <hofrat@osadl.org>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev,
Miguel Ojeda <ojeda@kernel.org>
Subject: [PATCH 2/2] time: fix references to _msecs_to_jiffies handling of values
Date: Fri, 25 Oct 2024 13:01:41 +0200 [thread overview]
Message-ID: <20241025110141.157205-2-ojeda@kernel.org> (raw)
In-Reply-To: <20241025110141.157205-1-ojeda@kernel.org>
The details about the handling of the "normal" values were moved
to the `_msecs_to_jiffies` helpers in commit ca42aaf0c861 ("time:
Refactor msecs_to_jiffies"). However, the same commit still mentioned
`__msecs_to_jiffies` in the added documentation.
Thus point to `_msecs_to_jiffies` instead.
Fixes: ca42aaf0c861 ("time: Refactor msecs_to_jiffies")
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
---
include/linux/jiffies.h | 2 +-
kernel/time/time.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/jiffies.h b/include/linux/jiffies.h
index 1220f0fbe5bf..5d21dacd62bc 100644
--- a/include/linux/jiffies.h
+++ b/include/linux/jiffies.h
@@ -502,7 +502,7 @@ static inline unsigned long _msecs_to_jiffies(const unsigned int m)
* - all other values are converted to jiffies by either multiplying
* the input value by a factor or dividing it with a factor and
* handling any 32-bit overflows.
- * for the details see __msecs_to_jiffies()
+ * for the details see _msecs_to_jiffies()
*
* msecs_to_jiffies() checks for the passed in value being a constant
* via __builtin_constant_p() allowing gcc to eliminate most of the
diff --git a/kernel/time/time.c b/kernel/time/time.c
index e1879ca32103..1ad88e97b4eb 100644
--- a/kernel/time/time.c
+++ b/kernel/time/time.c
@@ -556,7 +556,7 @@ EXPORT_SYMBOL(ns_to_timespec64);
* - all other values are converted to jiffies by either multiplying
* the input value by a factor or dividing it with a factor and
* handling any 32-bit overflows.
- * for the details see __msecs_to_jiffies()
+ * for the details see _msecs_to_jiffies()
*
* msecs_to_jiffies() checks for the passed in value being a constant
* via __builtin_constant_p() allowing gcc to eliminate most of the
--
2.47.0
next prev parent reply other threads:[~2024-10-25 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 11:01 [PATCH 1/2] time: revert cleanup on msecs_to_jiffies() documentation Miguel Ojeda
2024-10-25 11:01 ` Miguel Ojeda [this message]
2024-10-25 14:53 ` [tip: timers/core] time: Fix references to _msecs_to_jiffies() handling of values tip-bot2 for Miguel Ojeda
2024-10-25 18:01 ` tip-bot2 for Miguel Ojeda
2024-10-25 14:53 ` [tip: timers/core] time: Partially revert cleanup on msecs_to_jiffies() documentation tip-bot2 for Miguel Ojeda
2024-10-25 18:01 ` tip-bot2 for Miguel Ojeda
2024-10-26 19:32 ` [PATCH 1/2] time: " Randy Dunlap
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=20241025110141.157205-2-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=geert@linux-m68k.org \
--cc=hofrat@osadl.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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