From: Shuah Khan <shuahkh@osg.samsung.com>
To: Michal Marek <mmarek@suse.cz>, Michael Ellerman <mpe@ellerman.id.au>
Cc: Wang Long <long.wanglong@huawei.com>,
mmarek@suse.com, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, peifeiyue@huawei.com
Subject: Re: [PATCH v2] kselftest: add kselftest-clean rule
Date: Thu, 8 Oct 2015 07:26:19 -0600 [thread overview]
Message-ID: <56166EFB.7080708@osg.samsung.com> (raw)
In-Reply-To: <20151008122150.GA12217@sepie.suse.cz>
On 10/08/2015 06:21 AM, Michal Marek wrote:
> On Thu, Oct 08, 2015 at 02:52:04PM +1100, Michael Ellerman wrote:
>> On Thu, 2015-10-08 at 02:41 +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" kselftest-clean
>>>
>>> can clean all kselftest generated files.
>>>
>>> Signed-off-by: Wang Long <long.wanglong@huawei.com>
>>> ---
>>> Makefile | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>
>> Thanks that's much neater.
>>
>> Acked-by: Michael Ellerman <mpe@ellerman.id.au>
>
> Applied to kbuild.git#kbuild.
>
Thanks for getting this in.
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
prev parent reply other threads:[~2015-10-08 13:26 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
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 [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=56166EFB.7080708@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=long.wanglong@huawei.com \
--cc=mmarek@suse.com \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=peifeiyue@huawei.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;
as well as URLs for NNTP newsgroup(s).