From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>,
Lingzhu Xiang <lxiang@redhat.com>, Dave Young <dyoung@redhat.com>
Subject: Re: [PATCH 1/3 v3] selftests: Add tests for efivarfs
Date: Tue, 12 Feb 2013 15:48:02 -0800 [thread overview]
Message-ID: <20130212154802.186ed71a.akpm@linux-foundation.org> (raw)
In-Reply-To: <5114CE00.6050307@ozlabs.org>
On Fri, 08 Feb 2013 18:05:52 +0800
Jeremy Kerr <jk@ozlabs.org> wrote:
> > I'll do this for now:
> >
> > --- a/tools/testing/selftests/efivarfs/Makefile~selftests-add-tests-for-efivarfs-fix
> > +++ a/tools/testing/selftests/efivarfs/Makefile
> > @@ -6,7 +6,7 @@ test_objs = open-unlink
> > all: $(test_objs)
> >
> > run_tests: all
> > - @./efivarfs.sh || echo "efivarfs selftests: [FAIL]"
> > + @/bin/sh ./efivarfs.sh || echo "efivarfs selftests: [FAIL]"
> >
> > clean:
> > rm -f $(test_objs)
> >
> > but I'm not sure I did it right :(
>
> efivarfs.sh requires bash currently, so we'll need to call this explicitly:
>
> + @/bin/bash ./efivarfs.sh || echo "efivarfs selftests: [FAIL]"
>
> Is this okay?
Judging from ./Makefile:
# SHELL used by kbuild
CONFIG_SHELL := $(shell if [ -x "$$BASH" ]; then echo $$BASH; \
else if [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi ; fi)
bash is "optional" (this seems dumb, because all of us have
bash and we won't test /bin/sh).
But I expect that anyone who has an interest in running the selftests
is capable of making /bin/bash appear, so I'll make that change.
next prev parent reply other threads:[~2013-02-12 23:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 14:48 [PATCH 0/3 v3] selftests: Add efivarfs tests Jeremy Kerr
2013-02-06 14:48 ` [PATCH 1/3 v3] selftests: Add tests for efivarfs Jeremy Kerr
2013-02-07 23:13 ` Andrew Morton
2013-02-08 10:02 ` [PATCH] Documentation: Add a simple doc for selftests Jeremy Kerr
2013-02-12 23:56 ` Andrew Morton
2013-02-08 10:05 ` [PATCH 1/3 v3] selftests: Add tests for efivarfs Jeremy Kerr
2013-02-08 10:08 ` Matt Fleming
2013-02-12 23:50 ` Andrew Morton
2013-02-13 7:32 ` Matt Fleming
2013-02-12 23:48 ` Andrew Morton [this message]
2013-02-06 14:48 ` [PATCH 2/3 v3] selftests/efivarfs: Add empty file creation test Jeremy Kerr
2013-02-06 14:48 ` [PATCH 3/3 v3] selftests/efivarfs: Add create-read test Jeremy Kerr
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=20130212154802.186ed71a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lxiang@redhat.com \
--cc=matt.fleming@intel.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