public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@kernel.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>,
	John Stultz <jstultz@google.com>
Cc: linux-kernel@vger.kernel.org, Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: Re: [PATCH] alarmtimer: Fix kerneldoc comment for alarmtimer_suspend()
Date: Tue, 24 Feb 2026 09:48:19 +0100	[thread overview]
Message-ID: <87342qv86k.ffs@tglx> (raw)
In-Reply-To: <20260205085159.101801-1-zhanxusheng@xiaomi.com>

On Thu, Feb 05 2026 at 16:51, Zhan Xusheng wrote:
> Updated comment to explain that `dev` is used for scheduling
> wake-up events.

That's just wrong.

> Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
> ---
>  kernel/time/alarmtimer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/time/alarmtimer.c b/kernel/time/alarmtimer.c
> index 069d93bfb0c7..2548292b207d 100644
> --- a/kernel/time/alarmtimer.c
> +++ b/kernel/time/alarmtimer.c
> @@ -208,7 +208,7 @@ EXPORT_SYMBOL_GPL(alarm_expires_remaining);
>  #ifdef CONFIG_RTC_CLASS
>  /**
>   * alarmtimer_suspend - Suspend time callback
> - * @dev: unused
> + * @dev: the device that triggered the suspend, used for wake-up event

Which device triggered the suspend? Surely not @dev.

The code does not care about @dev as documented because it uses its
own mechanism to retrieve the wakeup RTC device.

So you replace a perfectly correct comment with incomprehensible
garbage. What's the improvement here?

Thanks,

        tglx



      reply	other threads:[~2026-02-24  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05  8:51 [PATCH] alarmtimer: Fix kerneldoc comment for alarmtimer_suspend() Zhan Xusheng
2026-02-24  8:48 ` Thomas Gleixner [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=87342qv86k.ffs@tglx \
    --to=tglx@kernel.org \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhanxusheng1024@gmail.com \
    --cc=zhanxusheng@xiaomi.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