From: shuah <shuah@kernel.org>
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Dmitry Safonov <0x7f454c46@gmail.com>,
linux-kselftest@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
shuah <shuah@kernel.org>
Subject: Re: [PATCH v3] selftests/timens: handle a case when alarm clocks are not supported
Date: Fri, 22 May 2020 13:32:23 -0600 [thread overview]
Message-ID: <a01519cf-9008-84fb-06ba-6f3f2288bee6@kernel.org> (raw)
In-Reply-To: <20200521075252.89475-1-avagin@gmail.com>
On 5/21/20 1:52 AM, Andrei Vagin wrote:
> This can happen if a testing node doesn't have RTC (real time clock)
> hardware or it doesn't support alarms.
>
> Fixes: 61c57676035d ("selftests/timens: Add Time Namespace test for supported clocks")
> Acked-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> Reported-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
> Signed-off-by: Andrei Vagin <avagin@gmail.com>
> ---
> v2: fix timer.c and timerfd.c too.
> v3: add Reported-by and Fixes tags.
>
> tools/testing/selftests/timens/clock_nanosleep.c | 2 +-
> tools/testing/selftests/timens/timens.c | 2 +-
> tools/testing/selftests/timens/timens.h | 13 ++++++++++++-
> tools/testing/selftests/timens/timer.c | 5 +++++
> tools/testing/selftests/timens/timerfd.c | 5 +++++
> 5 files changed, 24 insertions(+), 3 deletions(-)
>
Applied to linux-kselftest next for Linux 5.8-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2020-05-22 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 7:52 [PATCH v3] selftests/timens: handle a case when alarm clocks are not supported Andrei Vagin
2020-05-22 19:32 ` shuah [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=a01519cf-9008-84fb-06ba-6f3f2288bee6@kernel.org \
--to=shuah@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=avagin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.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