From: Shuah Khan <skhan@linuxfoundation.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Shuah Khan" <shuah@kernel.org>
Cc: Sebastian Reichel <sre@kernel.org>,
Mike Looijmans <mike.looijmans@topic.nl>,
kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2] selftests: Make sh helper and power supply test POSIX-compliant
Date: Wed, 24 Apr 2024 07:33:19 -0600 [thread overview]
Message-ID: <89605a09-3d19-427d-a368-374777449c1b@linuxfoundation.org> (raw)
In-Reply-To: <20240415-supply-selftest-posix-sh-v1-0-328f008d698d@collabora.com>
On 4/15/24 09:32, Nícolas F. R. A. Prado wrote:
> The patches in this series make the ktap sh helper and the power_supply
> selftest POSIX-compliant. Tested with bash, dash and busybox ash.
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> ---
> Nícolas F. R. A. Prado (2):
> selftests: ktap_helpers: Make it POSIX-compliant
> selftests: power_supply: Make it POSIX-compliant
>
> tools/testing/selftests/kselftest/ktap_helpers.sh | 4 ++--
> tools/testing/selftests/power_supply/test_power_supply_properties.sh | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
> ---
> base-commit: 7e74ee01d1754156ed3706b61e793fbd46f5cd7b
> change-id: 20240415-supply-selftest-posix-sh-aee99cf85e8f
>
> Best regards,
Thank you. Applied the patches to linux-kselftest next for Linux 6.10-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2024-04-24 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 15:32 [PATCH 0/2] selftests: Make sh helper and power supply test POSIX-compliant Nícolas F. R. A. Prado
2024-04-15 15:32 ` [PATCH 1/2] selftests: ktap_helpers: Make it POSIX-compliant Nícolas F. R. A. Prado
2024-04-15 18:38 ` Muhammad Usama Anjum
2024-04-15 15:32 ` [PATCH 2/2] selftests: power_supply: " Nícolas F. R. A. Prado
2024-04-15 18:38 ` Muhammad Usama Anjum
2024-04-24 13:33 ` 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=89605a09-3d19-427d-a368-374777449c1b@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=nfraprado@collabora.com \
--cc=shuah@kernel.org \
--cc=sre@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