From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
Binbin Wu <binbin.wu@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v2] selftests: x86: conform test to TAP format output
Date: Fri, 12 Jul 2024 12:28:50 +0500 [thread overview]
Message-ID: <e4d909d3-0021-455f-a2a7-e6546ebf6ffc@collabora.com> (raw)
In-Reply-To: <390d33da-1676-4b01-a7d5-8b5c2cc6a3a9@linuxfoundation.org>
On 7/11/24 9:39 PM, Shuah Khan wrote:
> On 7/11/24 00:52, Muhammad Usama Anjum wrote:
>> On 7/10/24 9:16 PM, Shuah Khan wrote:
>>> On 7/10/24 03:37, Muhammad Usama Anjum wrote:
>>>> This patch brings just readability implements by using kselftests wrappers
>>>> instead of manual pass/fail test cases counting. It has been on mailing
>>>> list from several months now. Please can someone ack or nack?
>>>>
>>>
>>> Okay. I think I responded to your other patches that are adding TAP
>>> to individual tests when kselftest wrapped does it for you based on
>>> return values.
>> The current test doesn't return any exit value (hence implicitly always 0
>> is returned). The return value in addition to some other changes is getting
>> fixed in this patch.
>
> Yes. Fixing the return the problems. Please send patches to do that
> and I will take them.
I'll send today.
>
> thanks,
> -- Shuah
>
>
--
BR,
Muhammad Usama Anjum
prev parent reply other threads:[~2024-07-12 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 10:18 [PATCH v2] selftests: x86: conform test to TAP format output Muhammad Usama Anjum
2024-05-28 5:05 ` Muhammad Usama Anjum
2024-07-01 8:38 ` Muhammad Usama Anjum
2024-07-10 9:37 ` Muhammad Usama Anjum
2024-07-10 16:16 ` Shuah Khan
2024-07-11 6:52 ` Muhammad Usama Anjum
2024-07-11 16:39 ` Shuah Khan
2024-07-12 7:28 ` Muhammad Usama Anjum [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=e4d909d3-0021-455f-a2a7-e6546ebf6ffc@collabora.com \
--to=usama.anjum@collabora.com \
--cc=binbin.wu@linux.intel.com \
--cc=chang.seok.bae@intel.com \
--cc=kernel@collabora.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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