From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Shuah Khan <shuah@kernel.org>,
Gautam <gautammenghani201@gmail.com>,
David Laight <David.Laight@ACULAB.COM>
Cc: kernel@collabora.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, kernelci@lists.linux.dev
Subject: Re: [PATCH v2] selftests: use printf instead of echo -ne
Date: Tue, 7 Feb 2023 09:36:30 +0100 [thread overview]
Message-ID: <97df8ef0-5eef-91cd-2d6d-eeff764c5e35@collabora.com> (raw)
In-Reply-To: <20230204135652.336495-1-guillaume.tucker@collabora.com>
On 04/02/2023 14:56, Guillaume Tucker wrote:
> On some systems, the default echo command doesn't handle the -e option
> and the output looks like this (arm64 build):
>
> -ne Emit Tests for alsa
>
> -ne Emit Tests for amd-pstate
>
> -ne Emit Tests for arm64
>
> This is for example the case with the KernelCI Docker images
> e.g. kernelci/gcc-10:x86-kselftest-kernelci. To avoid this issue, use
> printf which handles escape characters as a standard feature and is
> more widespread among modern shells.
>
> The output is now formatted as expected (x86 build this time):
>
> Emit Tests for alsa
> Emit Tests for amd-pstate
> Skipping non-existent dir: arm64
>
> Reported-by: "kernelci.org bot" <bot@kernelci.org>
> Suggested-by: David Laight <David.Laight@ACULAB.COM>
> Fixes: 3297a4df805d ("kselftests: Enable the echo command to print newlines in Makefile")
> Signed-off-by: Guillaume Tucker <guillaume.tucker@collabora.com>
> ---
>
> Notes:
> v2: use printf insead of $(which echo)
Oh I see you've already applied the v1 on kselftest/next branch:
79c16b1120fe selftests: find echo binary to use -ne options
Do you want me to send this printf fix rebased on top?
Thanks,
Guillaume
next prev parent reply other threads:[~2023-02-07 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 13:56 [PATCH v2] selftests: use printf instead of echo -ne Guillaume Tucker
2023-02-04 15:18 ` Guenter Roeck
2023-02-07 8:36 ` Guillaume Tucker [this message]
2023-02-07 21:54 ` 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=97df8ef0-5eef-91cd-2d6d-eeff764c5e35@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=David.Laight@ACULAB.COM \
--cc=gautammenghani201@gmail.com \
--cc=kernel@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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