From: Shuah Khan <skhan@linuxfoundation.org>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Shuah Khan <shuah@kernel.org>
Cc: kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: tpm2: redirect python unittest logs to stdout
Date: Thu, 1 Aug 2024 16:58:13 -0600 [thread overview]
Message-ID: <deda17e1-328f-4eed-b14b-84b47d36e8d7@linuxfoundation.org> (raw)
In-Reply-To: <D34XE10GQHIY.1H7BTET3DOREV@kernel.org>
On 8/1/24 16:24, Jarkko Sakkinen wrote:
> On Wed Jul 31, 2024 at 8:45 PM EEST, Shuah Khan wrote:
>> On 7/31/24 07:42, Muhammad Usama Anjum wrote:
>>> Reminder
>>>
>>
>> top post???
>>
>>> On 7/10/24 1:15 PM, Muhammad Usama Anjum wrote:
>>>> The python unittest module writes all its output to stderr, even when
>>>> the run is clean. Redirect its output logs to stdout.
>>>>
>>>> Cc: Jarkko Sakkinen <jarkko@kernel.org>
>>>> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
>>>> ---
>>>> tools/testing/selftests/tpm2/test_async.sh | 2 +-
>>>> tools/testing/selftests/tpm2/test_smoke.sh | 2 +-
>>>> tools/testing/selftests/tpm2/test_space.sh | 2 +-
>>>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>>>
>>
>> Applied to linux-kselftest next for Linux 6.12-rc1
>>
>> thanks,
>> -- Shuah
>
> OK, great. Maybe it is not *that* critical to backport this.
>
I took the liberty to pull this in. I agree that this doesn't need
backport. It suppresses messages and doesn't really fix any bug.
I tested it to make sure it doesn't suppress important messages.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-08-01 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 8:15 [PATCH] selftests: tpm2: redirect python unittest logs to stdout Muhammad Usama Anjum
2024-07-31 13:42 ` Muhammad Usama Anjum
2024-07-31 17:45 ` Shuah Khan
2024-08-01 22:24 ` Jarkko Sakkinen
2024-08-01 22:58 ` Shuah Khan [this message]
2024-08-02 17:46 ` Jarkko Sakkinen
2024-08-01 22:23 ` Jarkko Sakkinen
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=deda17e1-328f-4eed-b14b-84b47d36e8d7@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jarkko@kernel.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