linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "long.wanglong" <long.wanglong@huawei.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	mmarek@suse.com, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, wanglong@laoqinren.net,
	peifeiyue@huawei.com
Subject: Re: [PATCH] kselftest: add cleankselftest rule
Date: Thu, 8 Oct 2015 10:37:12 +0800	[thread overview]
Message-ID: <5615D6D8.8040208@huawei.com> (raw)
In-Reply-To: <560E9242.9000402@osg.samsung.com>

On 2015/10/2 22:18, Shuah Khan wrote:
> On 09/30/2015 07:17 PM, Michael Ellerman wrote:
>> On Wed, 2015-09-23 at 09:33 +0000, Wang Long wrote:
>>> We use
>>>
>>>     $make TARGETS="size timers" kselftest
>>>
>>> to build and run selftests. but there is no rule
>>> for us to clean the kselftest generated files.
>>>
>>> This patch add the rules, for example:
>>>
>>> 	$ make TARGETS="size timers" cleankselftest
>>
>> I think 'kselftest-clean' would be neater.
>>
>> That way all the kselftests targets start with 'kselftest'.
>>
> 
> Good suggestion. Wang! Could you please send me updated patch
> with this suggested change.

OK.

Since the National Day holiday, I am sorry so late reply.

I will send the updated patch.

Thanks.
> 
> thanks,
> -- Shuah
> 
> 



  reply	other threads:[~2015-10-08  2:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23  9:33 [PATCH] kselftest: add cleankselftest rule Wang Long
2015-09-30 13:36 ` Shuah Khan
2015-10-01  1:17 ` Michael Ellerman
2015-10-02 14:18   ` Shuah Khan
2015-10-08  2:37     ` long.wanglong [this message]
2015-10-08  2:41     ` [PATCH v2] kselftest: add kselftest-clean rule Wang Long
2015-10-08  3:52       ` Michael Ellerman
2015-10-08 12:21         ` Michal Marek
2015-10-08 13:26           ` 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=5615D6D8.8040208@huawei.com \
    --to=long.wanglong@huawei.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.com \
    --cc=mpe@ellerman.id.au \
    --cc=peifeiyue@huawei.com \
    --cc=shuahkh@osg.samsung.com \
    --cc=wanglong@laoqinren.net \
    /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;
as well as URLs for NNTP newsgroup(s).