From: Shuah Khan <shuahkh@osg.samsung.com>
To: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>, mmarek@suse.com
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org, yann.morin.1998@free.fr,
khilman@linaro.org, tyler.baker@linaro.org, broonie@kernel.org,
mpe@ellerman.id.au, dvhart@infradead.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v4 2/2] Makefile: add kselftest-merge
Date: Tue, 23 Feb 2016 11:31:32 -0700 [thread overview]
Message-ID: <56CCA584.9070504@osg.samsung.com> (raw)
In-Reply-To: <56CC6DDD.9080803@osg.samsung.com>
On 02/23/2016 07:34 AM, Shuah Khan wrote:
> On 01/08/2016 12:27 AM, Bamvor Jian Zhang wrote:
>> Add kselftest-merge to enable the dependencies of kernel config
>> for all the kselftest testcases. User should call it after create
>> the kernel configuration(.config), eg:
>>
>> $ make kselftest-merge
>>
>> Signed-off-by: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>
>
> Could you please ACK this patch if you are okay
> with the changes? I will take this through ksleftest
> tree.
>
> thanks,
> -- Shuah
Applied this patch to linux-kselftest next with
[PATCH v4 1/2] selftests: create test-specific kconfig fragments
to get some testing in for now.
thanks,
-- Shuah
--
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978
next prev parent reply other threads:[~2016-02-23 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 7:27 [PATCH v4 0/2] Create specific kconfig for kselftest Bamvor Jian Zhang
2016-01-08 7:27 ` [PATCH v4 1/2] selftests: create test-specific kconfig fragments Bamvor Jian Zhang
2016-02-23 18:28 ` Shuah Khan
2016-01-08 7:27 ` [PATCH v4 2/2] Makefile: add kselftest-merge Bamvor Jian Zhang
2016-02-23 14:34 ` Shuah Khan
2016-02-23 18:31 ` Shuah Khan [this message]
2016-02-12 16:10 ` [PATCH v4 0/2] Create specific kconfig for kselftest 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=56CCA584.9070504@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=broonie@kernel.org \
--cc=dvhart@infradead.org \
--cc=khilman@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=mpe@ellerman.id.au \
--cc=tyler.baker@linaro.org \
--cc=yann.morin.1998@free.fr \
/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