From: Shuah Khan <skhan@linuxfoundation.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Cc: kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/4] selftest: x86: conform tests to TAP format output
Date: Tue, 9 Jul 2024 17:39:54 -0600 [thread overview]
Message-ID: <fb305513-580a-4bac-a078-fe0170a6ffa2@linuxfoundation.org> (raw)
In-Reply-To: <23db41bb-1f3b-4b7b-95ac-960b8775a062@collabora.com>
On 7/2/24 04:17, Muhammad Usama Anjum wrote:
> On 6/10/24 10:19 AM, Muhammad Usama Anjum wrote:
>> Adding Borislav, Dave and x86 mailing list:
>> Please review the series.
> Kind reminder
>
Usama,
As I mentioned another TAP conversion patch from you patch if the
following command gives you TAP, there is no need to convert.
make -C tools/testing/tmp2 run_tests
make kselftest TARGETS=tmp2
kselftest framework lib.mk and runtests wrappers take care for
TAP. The reason to take care of this at framework level is to
avoid changes to individual tests. The wrapper keys off of
KSFT_* codes returned from tests.
Please don't send TAP conversion patches like this one. The output
from the commands will have duplicate messages. The reason tests
return
make -C tools/testing/tmp2 run_tests
make kselftest TARGETS=tmp2
thanks,
-- Shuah
next prev parent reply other threads:[~2024-07-09 23:39 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
2024-06-10 5:19 ` Muhammad Usama Anjum
2024-07-02 10:17 ` Muhammad Usama Anjum
2024-07-09 23:39 ` Shuah Khan [this message]
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=fb305513-580a-4bac-a078-fe0170a6ffa2@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--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 \
--cc=x86@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