From: Ian Campbell <ian.campbell@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Jonathan Creekmore <jonathan.creekmore@gmail.com>,
Keir Fraser <keir@xen.org>,
xen-devel@lists.xenproject.org, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH 0/4] Allow schedulers to be selectable through Kconfig
Date: Thu, 7 Jan 2016 15:31:23 +0000 [thread overview]
Message-ID: <1452180683.21055.247.camel@citrix.com> (raw)
In-Reply-To: <568E81DF.5060301@cardoe.com>
On Thu, 2016-01-07 at 09:18 -0600, Doug Goldstein wrote:
> > > With me asking for that option to not have a visible prompt by
> > > default,
> > > but nevertheless being settable. I do realize that this may not be
> > > possible with the current kconfig tool, but that's imo the only way
> > > to
> > > keep people from playing with expert options just because they see
> > > there's a prompt. No textual warning will help this, I'm afraid.
> >
> > While I have reasonably strong opinions about this issue, I do not
> > think
> > they warrant forking Kconfig over.
> >
> > With a suitably strong wording IMHO we have covered ourselves
> > sufficiently.
> >
> > Ian.
> >
>
> So Jonathan and I have been messing with the hidden option behind a
> non-menu option (e.g. environment variable). The only way we can get it
> to work is to require the environment variable to be passed at
> configuration time and at build time and I doubt you'd want the steps to
> be "CONFIG_EXPERT=n make menuconfig && CONFIG_EXPERT=n make" to build
> Xen. We'll play with this some more if that's desired but given Ian's
> response I don't know if it is.
You mean it has to be given as either =n or =y i.e. it has no default? I
don't think we can live with that indeed.
Ian.
next prev parent reply other threads:[~2016-01-07 15:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 20:59 [PATCH 0/4] Allow schedulers to be selectable through Kconfig Jonathan Creekmore
2015-12-17 20:59 ` [PATCH 1/4] build: Hook the schedulers into Kconfig Jonathan Creekmore
2015-12-18 1:35 ` Dario Faggioli
2015-12-18 2:20 ` Jonathan Creekmore
2015-12-18 9:19 ` Dario Faggioli
2015-12-18 10:52 ` George Dunlap
2015-12-18 11:23 ` Dario Faggioli
2015-12-18 8:57 ` Andrew Cooper
2015-12-18 16:43 ` Jonathan Creekmore
2015-12-17 20:59 ` [PATCH 2/4] build: Alloc space for sched list in the link file Jonathan Creekmore
2015-12-18 9:01 ` Andrew Cooper
2015-12-18 16:40 ` Jonathan Creekmore
2015-12-18 16:48 ` Andrew Cooper
2015-12-18 17:07 ` Jan Beulich
2015-12-18 17:10 ` Andrew Cooper
2015-12-18 17:11 ` Jonathan Creekmore
2015-12-18 17:23 ` Andrew Cooper
2015-12-17 20:59 ` [PATCH 3/4] sched: Register the schedulers into the list Jonathan Creekmore
2015-12-18 1:42 ` Dario Faggioli
2015-12-18 9:03 ` Andrew Cooper
2015-12-17 20:59 ` [PATCH 4/4] sched: Use the auto-generated list of schedulers Jonathan Creekmore
2015-12-18 1:47 ` Dario Faggioli
2015-12-18 9:12 ` Andrew Cooper
2015-12-18 16:44 ` Jonathan Creekmore
2015-12-18 10:50 ` Jan Beulich
2015-12-18 16:00 ` Jonathan Creekmore
2015-12-18 16:43 ` Jan Beulich
2015-12-18 17:24 ` Jonathan Creekmore
2015-12-18 17:30 ` Andrew Cooper
2015-12-18 10:39 ` [PATCH 0/4] Allow schedulers to be selectable through Kconfig Jan Beulich
2015-12-18 10:45 ` Ian Campbell
2015-12-18 10:58 ` Jan Beulich
2015-12-18 11:08 ` Juergen Gross
2015-12-18 11:19 ` Ian Campbell
2015-12-18 11:30 ` Jan Beulich
[not found] ` <5673FC6202000078000C122B@suse.com>
2015-12-18 11:41 ` Juergen Gross
2015-12-18 17:56 ` Doug Goldstein
2015-12-18 18:25 ` Andrew Cooper
2016-01-06 14:45 ` Ian Campbell
2016-01-07 14:01 ` Jonathan Creekmore
2016-01-07 14:37 ` Jan Beulich
2016-01-07 15:00 ` Ian Campbell
2016-01-07 15:18 ` Doug Goldstein
2016-01-07 15:31 ` Ian Campbell [this message]
2016-01-07 15:43 ` Jonathan Creekmore
2016-01-07 15:54 ` Jan Beulich
2016-01-07 15:47 ` Jan Beulich
2016-01-07 15:30 ` Ian Campbell
2016-01-07 15:51 ` Jan Beulich
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=1452180683.21055.247.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jonathan.creekmore@gmail.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).