From: Ian Campbell <Ian.Campbell@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Xen's Linux kernel config options V2
Date: Mon, 19 Jan 2015 13:28:39 +0000 [thread overview]
Message-ID: <1421674119.10440.91.camel@citrix.com> (raw)
In-Reply-To: <54905BF1.2050608@suse.com>
On Tue, 2014-12-16 at 17:21 +0100, Juergen Gross wrote:
> Option Selects Depends
> ----------------------------------------------------------------------
Could you annotate (maybe not a new column, perhaps with a * or
something) which options are supposed to be user-visible vs purely
internal things which can be selected?
I think it is still the case that selecting an option which is user
visible is frowned upon?
[...]
> The main difference to the current status is the XEN setting no longer
> controlling all other options.
In your list do the options which come under XEN or XEN_FRONTEND depend
on the respective headline config option?
Ian.
next prev parent reply other threads:[~2015-01-19 13:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 16:21 Xen's Linux kernel config options V2 Juergen Gross
2015-01-09 19:02 ` Konrad Rzeszutek Wilk
2015-02-04 0:48 ` Luis R. Rodriguez
2015-02-04 4:58 ` Juergen Gross
2015-02-05 23:59 ` Luis R. Rodriguez
2015-02-06 0:11 ` Luis R. Rodriguez
2015-02-04 8:29 ` Jan Beulich
2015-02-06 1:19 ` Luis R. Rodriguez
2015-01-19 13:28 ` Ian Campbell [this message]
2015-01-19 13:59 ` Jan Beulich
2015-02-04 0:50 ` Luis R. Rodriguez
2015-02-06 23:25 ` Luis R. Rodriguez
2015-02-06 23:26 ` Luis R. Rodriguez
2015-02-04 10:54 ` David Vrabel
2015-02-04 14:57 ` Stefano Stabellini
2015-02-04 15:02 ` Ian Campbell
2015-02-04 15:06 ` Stefano Stabellini
2015-02-06 1:28 ` Luis R. Rodriguez
2015-02-06 12:07 ` Stefano Stabellini
2015-02-06 22:51 ` Luis R. Rodriguez
2015-02-08 11:28 ` Stefano Stabellini
2015-02-12 4:29 ` Luis R. Rodriguez
2015-02-06 22:54 ` Luis R. Rodriguez
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=1421674119.10440.91.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.