From: Shuah Khan <skhan@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
greg@kroah.com, linux-kselftest@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH kselftest 0/3] getrandom & chacha cleanups
Date: Thu, 3 Oct 2024 16:42:42 -0600 [thread overview]
Message-ID: <8a64ac0a-9684-460d-aa68-31600be3e3f7@linuxfoundation.org> (raw)
In-Reply-To: <20241003031307.2236454-1-Jason@zx2c4.com>
On 10/2/24 21:13, Jason A. Donenfeld wrote:
> Hi Shuah,
>
> I've now read your email several times trying to figure out what you
> meant and what your objections are. This series is my best attempt at
> trying to satisfy that. But my understanding still has a lot of question
> marks, so I may have missed your point here. Nonetheless, maybe this
> moves things forward a bit.
>
> Jason
>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: Greg KH <greg@kroah.com>
>
> Jason A. Donenfeld (3):
> selftests: vDSO: condition chacha build on chacha implementation
> selftests: vDSO: unconditionally build getrandom test
> selftests: vDSO: improve getrandom and chacha error messages
>
> tools/testing/selftests/vDSO/Makefile | 4 +-
> .../testing/selftests/vDSO/vdso_test_chacha.c | 27 ++++---
> .../selftests/vDSO/vdso_test_getrandom.c | 75 ++++++++-----------
> 3 files changed, 52 insertions(+), 54 deletions(-)
>
Thank you Jason for fixing the problem. The patches look good
to me. I will run some tests and apply all 4 patches for next rc.
I did review the 4th patch as well.
https://patchwork.kernel.org/project/linux-kselftest/patch/20241003171852.2386463-1-Jason@zx2c4.com/
than
prev parent reply other threads:[~2024-10-03 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Zv20olVBlnxL9UnS@zx2c4.com>
2024-10-03 3:13 ` [PATCH kselftest 0/3] getrandom & chacha cleanups Jason A. Donenfeld
2024-10-03 3:13 ` [PATCH kselftest 1/3] selftests: vDSO: condition chacha build on chacha implementation Jason A. Donenfeld
2024-10-03 3:13 ` [PATCH kselftest 2/3] selftests: vDSO: unconditionally build getrandom test Jason A. Donenfeld
2024-10-03 3:13 ` [PATCH kselftest 3/3] selftests: vDSO: improve getrandom and chacha error messages Jason A. Donenfeld
2024-10-06 3:35 ` kernel test robot
2024-10-06 4:35 ` Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 1/4] selftests: vDSO: condition chacha build on chacha implementation Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 2/4] selftests: vDSO: unconditionally build getrandom test Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 3/4] selftests: vDSO: improve getrandom and chacha error messages Jason A. Donenfeld
2024-10-06 4:40 ` [PATCH kselftest v2 4/4] selftests: vDSO: unconditionally build chacha test Jason A. Donenfeld
2024-10-07 20:53 ` Shuah Khan
2024-10-07 21:45 ` [PATCH kselftest v3 1/3] " Jason A. Donenfeld
2024-10-07 21:45 ` [PATCH kselftest v3 2/3] selftests: vDSO: unconditionally build getrandom test Jason A. Donenfeld
2024-10-07 21:45 ` [PATCH kselftest v3 3/3] selftests: vDSO: improve getrandom and chacha error messages Jason A. Donenfeld
2024-10-08 21:36 ` [PATCH kselftest v3 1/3] selftests: vDSO: unconditionally build chacha test Shuah Khan
2024-10-03 17:18 ` [PATCH kselftest 4/3] " Jason A. Donenfeld
2024-10-03 22:42 ` Shuah Khan [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=8a64ac0a-9684-460d-aa68-31600be3e3f7@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=greg@kroah.com \
--cc=linux-kselftest@vger.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