From: Shuah Khan <skhan@linuxfoundation.org>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>, john.stultz@linaro.org
Cc: tglx@linutronix.de, sboyd@kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/timers: remove unneeded semicolon
Date: Fri, 26 Mar 2021 13:06:19 -0600 [thread overview]
Message-ID: <a5274488-2be2-9ef6-e01d-18da789a9881@linuxfoundation.org> (raw)
In-Reply-To: <1615276181-27090-1-git-send-email-jiapeng.chong@linux.alibaba.com>
On 3/9/21 12:49 AM, Jiapeng Chong wrote:
> Fix the following coccicheck warnings:
>
> ./tools/testing/selftests/timers/nanosleep.c:75:2-3: Unneeded semicolon
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> tools/testing/selftests/timers/nanosleep.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/timers/nanosleep.c b/tools/testing/selftests/timers/nanosleep.c
> index 71b5441..433a096 100644
> --- a/tools/testing/selftests/timers/nanosleep.c
> +++ b/tools/testing/selftests/timers/nanosleep.c
> @@ -72,7 +72,7 @@ char *clockstring(int clockid)
> return "CLOCK_BOOTTIME_ALARM";
> case CLOCK_TAI:
> return "CLOCK_TAI";
> - };
> + }
> return "UNKNOWN_CLOCKID";
> }
>
>
Can you send one single patch for all these timers fixes. All of these
patches have the same subject line and it is becoming hard to tell
them apart.
thanks,
-- Shuah
next prev parent reply other threads:[~2021-03-26 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 7:49 [PATCH] selftests/timers: remove unneeded semicolon Jiapeng Chong
2021-03-26 19:06 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-25 6:54 Jiapeng Chong
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=a5274488-2be2-9ef6-e01d-18da789a9881@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shuah@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