public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: Re: CONFIG_* used by user-space to figure out whether a feature is on/off
Date: Mon, 15 Jul 2013 15:03:11 -0400	[thread overview]
Message-ID: <20130715190311.GA3385@phenom.dumpdata.com> (raw)
In-Reply-To: <1373912743.2591.34.camel@x61.thuisdomein>

On Mon, Jul 15, 2013 at 08:25:43PM +0200, Paul Bolle wrote:
> On Mon, 2013-07-15 at 14:02 -0400, Konrad Rzeszutek Wilk wrote:
> > How about I make you proud and post a patch. See:
> > 
> >  http://article.gmane.org/gmane.comp.boot-loaders.grub.devel/20332 
> 
> And you're now also taking Michael's patch, that triggered this
> discussion, aren't you?

I believe there is a better way of doing this that I had enumerated
in the thread (see "xen: remove unused Kconfig parameter"). That was to
remove the CONFIG_XEN_PRIVILIGED and XEN_CONFIG_DOM0 and instead have an
CONFIG_XEN_HARDWARE_DOMAIN and CONFIG_XEN_CONTROL_DOMAIN which reflect the
reality a lot better.

P.S.
That idea had been percolating a bit - and it started way back with Andrew Jones
proposing an Kconfig patch a year ago - see:
http://lists.xen.org/archives/html/xen-devel/2012-01/msg00500.html for some
backstory.

  reply	other threads:[~2013-07-15 19:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 15:40 CONFIG_* used by user-space to figure out whether a feature is on/off Konrad Rzeszutek Wilk
2013-07-15 17:02 ` Greg KH
2013-07-15 17:24   ` Konrad Rzeszutek Wilk
2013-07-15 17:46     ` Linus Torvalds
2013-07-15 18:02       ` Konrad Rzeszutek Wilk
2013-07-15 18:25         ` Paul Bolle
2013-07-15 19:03           ` Konrad Rzeszutek Wilk [this message]
2013-07-15 19:13             ` Paul Bolle
2013-07-15 17:17 ` Linus Torvalds
2013-07-16  0:46   ` Raymond Jennings
2013-07-16  0:53     ` Linus Torvalds
2013-07-16  0:57       ` Raymond Jennings

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=20130715190311.GA3385@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=pebolle@tiscali.nl \
    --cc=torvalds@linux-foundation.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