From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: John Stultz <jstultz@google.com>
Cc: linux-renesas-soc@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/9] selftests: timers: fixes and improvements
Date: Thu, 14 Jul 2022 13:32:32 +0200 [thread overview]
Message-ID: <Ys/+0CVwtTpBNfws@shikoro> (raw)
In-Reply-To: <CANDhNCp3KhGjXSrS4xmqrdPJfxStZOOn+FQxJEEoiXZ39CxDpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
Hey John,
> Acked-by: John Stultz <jstultz@google.com>
>
> Thanks so much for submitting these.
Glad you like this series. I will wait some more to see if there are
further review comments. But surely, I will add the missing parameter to
the help output and add your tags to v2.
Thank you for doing these tools :)
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-07-14 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 20:46 [PATCH 0/9] selftests: timers: fixes and improvements Wolfram Sang
2022-07-13 20:46 ` [PATCH 1/9] selftests: timers: valid-adjtimex: build fix for newer toolchains Wolfram Sang
2022-07-13 20:46 ` [PATCH 2/9] selftests: timers: fix declarations of main() Wolfram Sang
2022-07-13 20:46 ` [PATCH 3/9] selftests: timers: nanosleep: adapt to kselftest framework Wolfram Sang
2022-07-13 20:46 ` [PATCH 4/9] selftests: timers: inconsistency-check: " Wolfram Sang
2022-07-13 20:46 ` [PATCH 5/9] selftests: timers: clocksource-switch: fix passing errors from child Wolfram Sang
2022-07-13 20:46 ` [PATCH 6/9] selftests: timers: clocksource-switch: sort includes Wolfram Sang
2022-07-13 20:46 ` [PATCH 7/9] selftests: timers: clocksource-switch: add command line switch to skip sanity check Wolfram Sang
2022-07-13 20:46 ` [PATCH 8/9] selftests: timers: clocksource-switch: add 'runtime' command line parameter Wolfram Sang
2022-07-13 21:05 ` John Stultz
2022-07-14 8:27 ` Sergei Shtylyov
2022-07-14 11:32 ` Wolfram Sang
2022-07-13 20:46 ` [PATCH 9/9] selftests: timers: clocksource-switch: adapt to kselftest framework Wolfram Sang
2022-07-13 21:02 ` [PATCH 0/9] selftests: timers: fixes and improvements John Stultz
2022-07-13 23:56 ` Shuah Khan
2022-07-14 18:43 ` Wolfram Sang
2022-07-14 20:47 ` Shuah Khan
2022-07-14 11:32 ` Wolfram Sang [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=Ys/+0CVwtTpBNfws@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=shuah@kernel.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