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 0/2] timers test fix and duplicate defines cleanup
Date: Thu, 26 Sep 2024 19:15:17 +0200 [thread overview]
Message-ID: <877cay2v6i.ffs@tglx> (raw)
In-Reply-To: <cover.1727191485.git.skhan@linuxfoundation.org>
On Tue, Sep 24 2024 at 09:56, Shuah Khan wrote:
> The first patch in this two patch fixes warn_unused_result compile
> time warning in posix_timers test.
>
> The second patch removes local NSEC_PER_SEC and USEC_PER_SEC defines.
> NSEC_PER_SEC and USEC_PER_SEC are defines in several timers tests.
> These defines are inconsistent with variations of ULL, LL, etc. without
> any explanation why it is necessary.
>
> These defines can be picked up from include/vdso/time64.h header
> file. In the interest of making it easier to maintain, remove the
> local defines. Include include/vdso/time64.h instead. This change
> will also make the defines consistent.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
prev parent reply other threads:[~2024-09-26 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 15:56 [PATCH 0/2] timers test fix and duplicate defines cleanup Shuah Khan
2024-09-24 15:56 ` [PATCH 1/2] selftests:timers: posix_timers: Fix warn_unused_result in __fatal_error() Shuah Khan
2024-09-25 15:13 ` Shuah Khan
2024-09-25 17:19 ` John Stultz
2024-09-24 15:56 ` [PATCH 2/2] selftests: timers: Remove local NSEC_PER_SEC and USEC_PER_SEC defines Shuah Khan
2024-09-24 23:59 ` John Stultz
2024-09-25 15:20 ` Shuah Khan
2024-09-25 17:33 ` John Stultz
2024-09-26 17:15 ` 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=877cay2v6i.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