From: Ingo Molnar <mingo@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, John Stultz <jstultz@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] time: fix various kernel-doc problems
Date: Tue, 3 Jan 2023 11:06:34 +0100 [thread overview]
Message-ID: <Y7P+KuMs52BTfKgv@gmail.com> (raw)
In-Reply-To: <20230103032849.12723-1-rdunlap@infradead.org>
* Randy Dunlap <rdunlap@infradead.org> wrote:
> kernel/time/tick-oneshot.c:107: warning: expecting prototype for tick_check_oneshot_mode(). Prototype was for tick_oneshot_mode_active() instead
> --- a/kernel/time/tick-oneshot.c
> +++ b/kernel/time/tick-oneshot.c
> @@ -103,7 +103,7 @@ int tick_switch_to_oneshot(void (*handle
> *
> * returns 1 when either nohz or highres are enabled. otherwise 0.
> */
> -int tick_oneshot_mode_active(void)
> +int tick_check_oneshot_mode(void)
> {
> unsigned long flags;
> int ret;
This one looks wrong - did you change the name on the wrong line?
I've applied your patch, but fixed the above hunk to be:
@@ -99,7 +99,7 @@ int tick_switch_to_oneshot(void (*handle
}
/**
- * tick_check_oneshot_mode - check whether the system is in oneshot mode
+ * tick_oneshot_mode_active - check whether the system is in oneshot mode
*
* returns 1 when either nohz or highres are enabled. otherwise 0.
*/
Thanks,
Ingo
next prev parent reply other threads:[~2023-01-03 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 3:28 [PATCH] time: fix various kernel-doc problems Randy Dunlap
2023-01-03 5:21 ` kernel test robot
2023-01-03 5:41 ` kernel test robot
2023-01-03 6:01 ` kernel test robot
2023-01-03 10:06 ` Ingo Molnar [this message]
2023-01-03 16:54 ` Randy Dunlap
2023-01-03 10:31 ` [tip: timers/urgent] time: Fix " tip-bot2 for 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=Y7P+KuMs52BTfKgv@gmail.com \
--to=mingo@kernel.org \
--cc=fweisbec@gmail.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--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