linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Bamvor Jian Zhang
	<bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org,
	tyler.baker-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org,
	dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [PATCH RFD] selftests: create test-specific kconfig fragments
Date: Mon, 16 Nov 2015 14:32:00 -0800	[thread overview]
Message-ID: <7hpoz9a84f.fsf@linaro.org> (raw)
In-Reply-To: <1447477033-7522-1-git-send-email-bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> (Bamvor Jian Zhang's message of "Sat, 14 Nov 2015 12:57:13 +0800")

Hi Bamvor,

Bamvor Jian Zhang <bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> writes:

> There is a discussion about improving the usability of kselftest by
> creating test-specific kconfig in recent kernel Summit. Furthormore,
> there are different approaches to do it:
>
> 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).
>
> 2) In the main menu, have an additional option/flag for each feature
> that should be enabled when ksefltests are wanted.  Similar to the
> CONFIG_COMPILE_TEST flag.
>
> This patch try to do option 1. Hope it is a good start for
> discussion. User could use these configs with merge_config.sh script:

For broader discussion, could you please resend and include LKML?

Thanks,

Kevin

  parent reply	other threads:[~2015-11-16 22:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-14  4:57 [PATCH RFD] selftests: create test-specific kconfig fragments Bamvor Jian Zhang
     [not found] ` <1447477033-7522-1-git-send-email-bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-11-16 22:32   ` Kevin Hilman [this message]
     [not found]     ` <7hpoz9a84f.fsf-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-11-16 23:06       ` Michael Ellerman
     [not found]         ` <1447715190.23280.1.camel-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
2015-11-16 23:30           ` Bamvor Zhang Jian
     [not found]             ` <CAFy1USTNWoC_J0VgWEzA8f4WabgXgbAaBT=OPPWrz9M45gKK6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-16 23:42               ` Michael Ellerman
     [not found]                 ` <1447717377.23280.3.camel-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org>
2015-11-17  0:20                   ` Bamvor Zhang Jian
2015-11-16 23:40       ` Bamvor Zhang Jian

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=7hpoz9a84f.fsf@linaro.org \
    --to=khilman-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=bamvor.zhangjian-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=dvhart-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mpe-Gsx/Oe8HsFggBc27wqDAHg@public.gmane.org \
    --cc=shuahkh-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org \
    --cc=tyler.baker-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).