From: Michael Ellerman <mpe@ellerman.id.au>
To: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>,
linux-api@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
shuahkh@osg.samsung.com, yann.morin.1998@free.fr,
khilman@linaro.org, tyler.baker@linaro.org, broonie@kernel.org,
dvhart@infradead.org
Subject: Re: [PATCH v3 0/2] Create specific kconfig for kselftest
Date: Fri, 18 Dec 2015 10:44:57 +1100 [thread overview]
Message-ID: <1450395897.19696.0.camel@ellerman.id.au> (raw)
In-Reply-To: <1450346273-31633-1-git-send-email-bamvor.zhangjian@linaro.org>
On Thu, 2015-12-17 at 17:57 +0800, Bamvor Jian Zhang wrote:
> There is a discussion about improving the usability of kselftest by
> creating test-specific kconfig in recent kernel Summit.
>
> Patch 1 keep test-specific kconfig fragments inside each selftest so
> that merge_configs.sh could build up a kernel that can test the
> specific or all feature(s).
>
> Patch 2 add config option(kselftest-mergeconfig) in make file as a
> helper to merge all the test config dependecies to .config.
>
> Changes since v2:
> 1. Fix the misuse of objtree and srctree in the
> kselftest-mergeconfig target.
>
> Changes since v1:
> 1. Add kselftest-mergeconfig in scripts/kconfig/Makefile according
> to the suggestion from Michael.
Sorry I only just noticed you put it in scripts/kconfig/Makefile. I meant for
it to go in Makefile, alongside the other kselftest targets.
cheers
next prev parent reply other threads:[~2015-12-17 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 9:57 Bamvor Jian Zhang
2015-12-17 9:57 ` Bamvor Jian Zhang
2015-12-17 9:57 ` [PATCH v3 1/2] selftests: create test-specific kconfig fragments Bamvor Jian Zhang
2015-12-17 9:57 ` [PATCH v3 2/2] scripts/kconfig/Makefile: add kselftest-mergeconfig Bamvor Jian Zhang
2015-12-17 23:44 ` Michael Ellerman [this message]
2015-12-24 10:17 ` [PATCH v3 0/2] Create specific kconfig for kselftest Bamvor Zhang Jian
2016-01-04 4:57 ` Michael Ellerman
2016-01-04 10:34 ` Bamvor Jian Zhang
2016-01-05 0:17 ` Michael Ellerman
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=1450395897.19696.0.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=bamvor.zhangjian@linaro.org \
--cc=broonie@kernel.org \
--cc=dvhart@infradead.org \
--cc=khilman@linaro.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--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
all inboxes | Powered by JetHome®