From: Shuah Khan <shuah.kh@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>, Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
"sam@ravnborg.org >> Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: [PATCH] kbuild: devtest - new make target for build all and run tests
Date: Thu, 07 Aug 2014 07:59:31 -0600 [thread overview]
Message-ID: <53E38643.2010108@samsung.com> (raw)
In-Reply-To: <20140806143149.GA13552@kroah.com>
On 08/06/2014 08:31 AM, Greg KH wrote:
> On Wed, Aug 06, 2014 at 04:06:33PM +0200, Michal Marek wrote:
>> On 2014-08-06 16:04, Shuah Khan wrote:
>>> On 08/06/2014 07:51 AM, Michal Marek wrote:
>>>> On 2014-07-18 22:44, 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.
>>>>
>>>> I agree with Sam that the name is rather ambiguous, but I can't suggest
>>>> a better alternative right now.
>>>
>>> Does kselftest or kern_selftest sound better?
>>
>> It does sound better to me than dev(ice)test, but I'm not a native
>> English speaker. Greg?
>
> Either is fine with me, but I don't think we have '_' as any make target
> today, so perhaps "kselftest" is best?
>
> thanks,
>
> greg k-h
>
Patch v2 is on its way. kselftest is the new target. It does sound lot
better than devtest :)
-- Shuah
--
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah.kh@samsung.com | (970) 672-0658
prev parent reply other threads:[~2014-08-07 13:59 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
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 [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=53E38643.2010108@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