From: Shuah Khan <skhan@linuxfoundation.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kernel@collabora.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/4] selftest: x86: conform tests to TAP format output
Date: Fri, 7 Jun 2024 14:52:12 -0600 [thread overview]
Message-ID: <90dc0dfc-4c67-4ea1-b705-0585d6e2ec47@linuxfoundation.org> (raw)
In-Reply-To: <dd277b6b-b28e-4860-b285-e89fd5fd3d41@collabora.com>
On 5/27/24 23:04, Muhammad Usama Anjum wrote:
> Kind reminder
>
> On 4/14/24 6:18 PM, Muhammad Usama Anjum wrote:
>> In this series, 4 tests are being conformed to TAP.
>>
>> Muhammad Usama Anjum (4):
>> selftests: x86: check_initial_reg_state: conform test to TAP format
>> output
>> selftests: x86: corrupt_xstate_header: conform test to TAP format
>> output
>> selftests: fsgsbase_restore: conform test to TAP format output
>> selftests: entry_from_vm86: conform test to TAP format output
>>
>> .../selftests/x86/check_initial_reg_state.c | 24 ++--
>> .../selftests/x86/corrupt_xstate_header.c | 30 +++--
>> tools/testing/selftests/x86/entry_from_vm86.c | 109 ++++++++--------
>> .../testing/selftests/x86/fsgsbase_restore.c | 117 +++++++++---------
>> 4 files changed, 139 insertions(+), 141 deletions(-)
>>
>
These patches usually go through x86 repo to avoid merge conflicts.
I need ack from x86 maintainers to take these. I don't see x86 list
cc'ed.
Please make sure to include everybody on these threads to get quicker
response.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-06-07 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 13:18 [PATCH 0/4] selftest: x86: conform tests to TAP format output Muhammad Usama Anjum
2024-04-14 13:18 ` [PATCH 1/4] selftests: x86: check_initial_reg_state: conform test " Muhammad Usama Anjum
2024-04-14 13:18 ` [PATCH 2/4] selftests: x86: corrupt_xstate_header: " Muhammad Usama Anjum
2024-04-14 13:18 ` [PATCH 3/4] selftests: fsgsbase_restore: " Muhammad Usama Anjum
2024-04-14 13:18 ` [PATCH 4/4] selftests: entry_from_vm86: " Muhammad Usama Anjum
2024-04-22 12:36 ` [PATCH 0/4] selftest: x86: conform tests " Muhammad Usama Anjum
2024-05-28 5:02 ` Muhammad Usama Anjum
2024-05-28 5:04 ` Muhammad Usama Anjum
2024-06-07 20:52 ` Shuah Khan [this message]
2024-06-10 5:19 ` Muhammad Usama Anjum
2024-07-02 10:17 ` Muhammad Usama Anjum
2024-07-09 23:39 ` Shuah Khan
2024-07-10 8:58 ` Muhammad Usama Anjum
2024-07-11 16:14 ` Shuah Khan
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=90dc0dfc-4c67-4ea1-b705-0585d6e2ec47@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=usama.anjum@collabora.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