From: Shuah Khan <shuah.kh@samsung.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: mmarek@suse.cz, gregkh@linuxfoundation.org,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: devtest - new make target for build all and run tests
Date: Fri, 18 Jul 2014 18:13:08 -0600 [thread overview]
Message-ID: <53C9B814.4020809@samsung.com> (raw)
In-Reply-To: <20140718232958.GA22487@ravnborg.org>
On 07/18/2014 05:29 PM, Sam Ravnborg wrote:
> On Fri, Jul 18, 2014 at 02:44:34PM -0600, Shuah Khan wrote:
>> Add a new devtest make target to enable developer testing. This
>> new target does full build (make all) and then runs selftests.
>>
>> Signed-off-by: Shuah Khan <shuah.kh@samsung.com>
>> ---
>> Makefile | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/Makefile b/Makefile
>> index f3c543d..1ef3128 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -1034,6 +1034,14 @@ headers_check: headers_install
>> $(Q)$(MAKE) $(hdr-inst)=arch/$(hdr-arch)/include/uapi/asm $(hdr-dst) HDRCHECK=1
>>
>> # ---------------------------------------------------------------------------
>> +# Kernel devtest
>> +
>> +PHONY += devtest
>> +devtest:
>> + make all
>> + make -C tools/testing/selftests run_tests
>
> The name "devtest" does not give any hints that we are actually
> running the suite of selftest programs.
>
> Is it so because the plan is to extend devtest to cover more than just selftest?
> If not please fix it so it is logical for the user what happens - in other
> words name is selftest or something like that.
>
Yes the intent is to cover more than just selftests in the future.
That is why the target is called devtest.
-- Shuah
--
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah.kh@samsung.com | (970) 672-0658
next prev parent reply other threads:[~2014-07-19 0:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 20:44 [PATCH] kbuild: devtest - new make target for build all and run tests Shuah Khan
2014-07-18 21:06 ` Greg KH
2014-07-18 23:29 ` Sam Ravnborg
2014-07-19 0:13 ` Shuah Khan [this message]
2014-08-06 13:41 ` Shuah Khan
2014-08-06 13:51 ` Michal Marek
2014-08-06 14:04 ` Shuah Khan
2014-08-06 14:06 ` Michal Marek
2014-08-06 14:31 ` Greg KH
2014-08-07 13:59 ` 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=53C9B814.4020809@samsung.com \
--to=shuah.kh@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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