From: Michael Ellerman <mpe@ellerman.id.au>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, davej@codemonkey.org.uk,
mmarek@suse.cz, linux-api@vger.kernel.org
Subject: Re: [PATCH v4 4/9] selftests: Add install target
Date: Mon, 16 Mar 2015 14:12:57 +1100 [thread overview]
Message-ID: <1426475577.20210.8.camel@ellerman.id.au> (raw)
In-Reply-To: <1426475092.20210.4.camel@ellerman.id.au>
On Mon, 2015-03-16 at 14:04 +1100, Michael Ellerman wrote:
> On Fri, 2015-03-13 at 15:32 -0600, Shuah Khan wrote:
> > On 03/13/2015 11:20 AM, Shuah Khan wrote:
> > > On 03/10/2015 10:06 PM, Michael Ellerman wrote:
> > >> This adds make install support to selftests. The basic usage is:
> > >>
> > >> $ cd tools/testing/selftests
> > >> $ make install
> > >>
> > >> That installs into tools/testing/selftests/install, which can then be
> > >> copied where ever necessary.
> > >>
> > >> The install destination is also configurable using eg:
> > >>
> > >> $ INSTALL_PATH=/mnt/selftests make install
> > >>
> > >> The implementation uses two targets in the child makefiles. The first
> > >> "install" is expected to install all files into $(INSTALL_PATH).
> > >>
> > >> The second, "emit_tests", is expected to emit the test instructions (ie.
> > >> bash script) on stdout. Separating this from install means the child
> > >> makefiles need no knowledge of the location of the test script.
> > >>
> > >> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> > >
> > > Thanks for doing the work. This patch will be applied to next and will
> > > be queued for 4.1
> > >
> >
> > ok. linux-kselftest next has both shared logic and install patches
> > now.
>
> Thanks, looks good to me.
And also 6/9 "selftests: Set CC using CROSS_COMPILE once in lib.mk" would be
nice and is uncontroversial, I think:
https://lkml.org/lkml/2015/3/11/5
cheers
next prev parent reply other threads:[~2015-03-16 3:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 4:05 [PATCH v4 1/9] kbuild: Don't pass -rR to selftest makefiles Michael Ellerman
2015-03-11 4:05 ` [PATCH v4 2/9] kbuild: Don't pass LDFLAGS to selftest Makefile Michael Ellerman
2015-03-11 16:08 ` Shuah Khan
2015-03-13 18:06 ` Shuah Khan
2015-03-11 4:05 ` [PATCH v4 3/9] selftests: Introduce minimal shared logic for running tests Michael Ellerman
2015-03-13 17:19 ` Shuah Khan
2015-03-13 20:28 ` Shuah Khan
2015-03-11 4:06 ` [PATCH v4 4/9] selftests: Add install target Michael Ellerman
2015-03-11 13:18 ` Shuah Khan
2015-03-11 16:03 ` Shuah Khan
2015-03-12 3:11 ` Michael Ellerman
2015-03-12 3:15 ` Michael Ellerman
2015-03-13 16:33 ` Dave Jones
2015-03-13 17:08 ` Shuah Khan
2015-03-13 17:20 ` Shuah Khan
2015-03-13 21:32 ` Shuah Khan
2015-03-13 23:08 ` Shuah Khan
2015-03-16 3:04 ` Michael Ellerman
2015-03-16 3:12 ` Michael Ellerman [this message]
2015-03-18 14:30 ` Shuah Khan
2015-03-11 4:06 ` [PATCH v4 5/9] selftests: Add install support for the powerpc tests Michael Ellerman
2015-03-11 4:06 ` [PATCH v4 6/9] selftests: Set CC using CROSS_COMPILE once in lib.mk Michael Ellerman
2015-03-11 4:06 ` [PATCH v4 7/9] selftests/timers: Use implicit rules Michael Ellerman
2015-03-11 4:06 ` [PATCH v4 8/9] selftests/mqueue: " Michael Ellerman
2015-03-11 4:06 ` [PATCH v4 9/9] selftests/mount: " Michael Ellerman
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=1426475577.20210.8.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=davej@codemonkey.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=shuahkh@osg.samsung.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
Powered by JetHome