From: Thomas Gleixner <tglx@linutronix.de>
To: Shuah Khan <skhan@linuxfoundation.org>,
jstultz@google.com, sboyd@kernel.org, shuah@kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests:timers: remove local CLOCKID defines
Date: Tue, 15 Oct 2024 00:03:23 +0200 [thread overview]
Message-ID: <87zfn6e40k.ffs@tglx> (raw)
In-Reply-To: <20241011225236.27677-1-skhan@linuxfoundation.org>
On Fri, Oct 11 2024 at 16:52, Shuah Khan wrote:
> timers tests defines CLOCKIDs locally. Remove all local CLOCKIDs except
> CLOCK_HWSPECIFIC and use defines from time.h header file.
>
> CLOCK_HWSPECIFIC and CLOCK_SGI_CYCLE are the same and CLOCK_SGI_CYCLE
> is deprecated,
>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Thank you!
prev parent reply other threads:[~2024-10-14 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 22:52 [PATCH] selftests:timers: remove local CLOCKID defines Shuah Khan
2024-10-12 0:49 ` John Stultz
2024-10-14 22:09 ` Shuah Khan
2024-10-14 22:03 ` 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=87zfn6e40k.ffs@tglx \
--to=tglx@linutronix.de \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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