From: Caleb James DeLisle <cjd@cjdns.fr>
To: Chen Ni <nichen@iscas.ac.cn>,
daniel.lezcano@linaro.org, tglx@linutronix.de
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource/timer-econet-en751221: Convert comma to semicolon
Date: Tue, 3 Jun 2025 12:05:17 +0200 [thread overview]
Message-ID: <c40fd836-ac63-48d0-93aa-8dd5f3dbcf79@cjdns.fr> (raw)
In-Reply-To: <20250603060450.1310204-1-nichen@iscas.ac.cn>
On 03/06/2025 08:04, Chen Ni wrote:
> Replace comma between expressions with semicolons.
>
> Using a ',' in place of a ';' can have unintended side effects.
> Although that is not the case here, it is seems best to use ';'
> unless ',' is intended.
>
> Found by inspection.
> No functional change intended.
> Compile tested only.
>
> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
Tested-by: Caleb James DeLisle <cjd@cjdns.fr>
The comma was indeed unintended, thank you.
Caleb
> ---
> drivers/clocksource/timer-econet-en751221.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/timer-econet-en751221.c b/drivers/clocksource/timer-econet-en751221.c
> index 3b449fdaafee..4008076b1a21 100644
> --- a/drivers/clocksource/timer-econet-en751221.c
> +++ b/drivers/clocksource/timer-econet-en751221.c
> @@ -146,7 +146,7 @@ static int __init cevt_init(struct device_node *np)
> for_each_possible_cpu(i) {
> struct clock_event_device *cd = &per_cpu(econet_timer_pcpu, i);
>
> - cd->rating = 310,
> + cd->rating = 310;
> cd->features = CLOCK_EVT_FEAT_ONESHOT |
> CLOCK_EVT_FEAT_C3STOP |
> CLOCK_EVT_FEAT_PERCPU;
next prev parent reply other threads:[~2025-06-03 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 6:04 Chen Ni
2025-06-03 10:05 ` Caleb James DeLisle [this message]
2025-07-15 11:24 ` Daniel Lezcano
2025-07-23 7:17 ` [tip: timers/clocksource] " tip-bot2 for Chen Ni
2025-07-25 10:31 ` tip-bot2 for Chen Ni
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=c40fd836-ac63-48d0-93aa-8dd5f3dbcf79@cjdns.fr \
--to=cjd@cjdns.fr \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nichen@iscas.ac.cn \
--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
all inboxes | Powered by JetHome®