From: Hangbin Liu <liuhangbin@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: Shuah Khan <shuah@kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
linux-doc@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Tim.Bird@sony.com, lkft-triage@lists.linaro.org,
Anders Roxell <anders.roxell@linaro.org>,
Justin Cook <justin.cook@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCHv5 kselftest next] selftests/run_kselftest.sh: make each test individually selectable
Date: Tue, 29 Sep 2020 09:27:31 +0800 [thread overview]
Message-ID: <20200929012731.GE2531@dhcp-12-153.nay.redhat.com> (raw)
In-Reply-To: <202009281305.E6F9595@keescook>
On Mon, Sep 28, 2020 at 01:06:15PM -0700, Kees Cook wrote:
> > I'm really sorry to make this trouble. And I'm OK to revert the patch.
> > I just a little wondering how do you generate this script.
>
> This issue is with which shell is used. I suspect your /bin/sh is full
> /bin/bash, where as Naresh's, the CI's, and mine are /bin/dash (which
> lacks "-e" support for the built-in "echo").
Ah, got it. Thanks for your explanation.
Regards
Hangbin
prev parent reply other threads:[~2020-09-29 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200914021758.420874-1-liuhangbin@gmail.com/>
2020-09-14 2:22 ` [PATCHv5 kselftest next] selftests/run_kselftest.sh: make each test individually selectable Hangbin Liu
2020-09-25 8:21 ` Naresh Kamboju
2020-09-25 21:16 ` Kees Cook
2020-09-25 22:37 ` Shuah Khan
2020-09-25 23:06 ` Shuah Khan
2020-09-25 23:46 ` Kees Cook
2020-09-27 1:53 ` Hangbin Liu
2020-09-28 20:06 ` Kees Cook
2020-09-29 1:27 ` Hangbin Liu [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=20200929012731.GE2531@dhcp-12-153.nay.redhat.com \
--to=liuhangbin@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=anders.roxell@linaro.org \
--cc=corbet@lwn.net \
--cc=justin.cook@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.