From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: yamada.masahiro@socionext.com, mmarek@suse.com, shuah@kernel.org,
tglx@linutronix.de, mingo@redhat.com, peterz@infradead.org,
bamvor.zhangjian@linaro.org, emilio.lopez@collabora.co.uk,
corbet@lwn.net, tytso@mit.edu, ebiederm@xmission.com,
Tim.Bird@sony.com, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 00/11] Kselftest make O=dir work
Date: Tue, 12 Sep 2017 17:58:21 -0700 [thread overview]
Message-ID: <20170913005821.GB22110@kroah.com> (raw)
In-Reply-To: <cover.1505257614.git.shuahkh@osg.samsung.com>
On Tue, Sep 12, 2017 at 05:52:53PM -0600, Shuah Khan wrote:
> During [MAINTAINERS SUMMIT] & [TECH TOPIC] Improve regression tracking
> discussion, it was brought to my attention that kselftest lacks support
> for make O=dir use-case which is used by several developers to relocate
> objects and keep the source tree clean.
>
> I mentioned in thread that I would take a look at what it takes to support
> it and here is the patch series that does that.
>
> This 11 patch series consists of fixes to get "make O=dir kselftest"
> use-case working, extending the existing KBUILD_OUTPUT support.
> Majority of the changes are made to kselftest common infrastructure.
> Some test make files are changed as needed to address the custom build
> and run_tests.
>
> -- futex has sub-directories which require custom build and run_tests.
> -- sync test needed a few changes to make use of lib.mk as much as possible
> and still be able to run its custom build sequence.
>
> With this series the following ways to build and run kselftest is possible:
>
> -- Build all and Relocate objects to /tmp/kselftest and run tests:
> make O=/tmp/kselftest kselftest
> or
> make KBUILD_OUTPUT=/tmp/kselftest kselftest
>
> -- Build TARGETS and Relocate objects to /tmp/kselftest and run tests:
> make O=/tmp/kselftest TARGETS="futex sync size" kselftest
> or
> make KBUILD_OUTPUT=/tmp/kselftest TARGETS="futex sync size" kselftest
>
> -- Clean tests:
> make O=/tmp/kselftest kselftest-clean
> or
> make KBUILD_OUTPUT=/tmp/kselftest kselftest-clean
>
> All existing use-cases documented in Documentation/dev-tools/kselftest.rst
> are still supported.
Yeah! Nice work.
greg k-h
prev parent reply other threads:[~2017-09-13 0:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 23:52 [PATCH 00/11] Kselftest make O=dir work Shuah Khan
2017-09-12 23:52 ` [PATCH 01/11] Makefile: kselftest and kselftest-clean fail for make O=dir case Shuah Khan
2017-09-18 23:14 ` Shuah Khan
2017-09-20 3:39 ` Masahiro Yamada
2017-09-20 17:30 ` Shuah Khan
2017-09-12 23:52 ` [PATCH 02/11] selftests: lib.mk: " Shuah Khan
2017-09-12 23:52 ` [PATCH 03/11] selftests: Makefile: clear LDFLAGS for make O=dir use-case Shuah Khan
2017-09-12 23:52 ` [PATCH 04/11] selftests: lib.mk: fix test executable status check to use full path Shuah Khan
2017-09-12 23:52 ` [PATCH 05/11] selftests: watchdog: fix to use TEST_GEN_PROGS and remove clean Shuah Khan
2017-09-12 23:52 ` [PATCH 06/11] selftests: lib.mk: add TEST_CUSTOM_PROGS to allow custom test run/install Shuah Khan
2017-09-12 23:53 ` [PATCH 07/11] selftests: sync: use TEST_CUSTOM_PROGS instead of TEST_PROGS Shuah Khan
2017-09-12 23:53 ` [PATCH 08/11] selftests: sync: kselftest and kselftest-clean fail for make O=dir case Shuah Khan
2017-09-12 23:53 ` [PATCH 09/11] selftests: lib.mk: copy test scripts and test files for make O=dir run Shuah Khan
2017-09-13 18:14 ` Bird, Timothy
2017-09-13 19:43 ` Shuah Khan
2017-09-12 23:53 ` [PATCH 10/11] selftests: futex: copy sub-dir test scripts " Shuah Khan
2017-09-13 18:15 ` Bird, Timothy
2017-09-23 0:36 ` Darren Hart
2017-09-12 23:53 ` [PATCH 11/11] selftests: mqueue: Use full path to run tests from Makefile Shuah Khan
2017-09-13 0:58 ` Greg KH [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=20170913005821.GB22110@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Tim.Bird@sony.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=emilio.lopez@collabora.co.uk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=yamada.masahiro@socionext.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