mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
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 21:13:58 +0200	[thread overview]
Message-ID: <1373915638.2591.45.camel@x61.thuisdomein> (raw)
In-Reply-To: <20130715190311.GA3385@phenom.dumpdata.com>

On Mon, 2013-07-15 at 15:03 -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 15, 2013 at 08:25:43PM +0200, Paul Bolle wrote:
> > 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.

But, whatever you choose to do in the future, that needn't stop you from
dropping XEN_PRIVILIGED_GUEST now. It's basically a trivial cleanup.


Paul Bolle


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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 15:40 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
2013-07-15 19:13             ` Paul Bolle [this message]
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=1373915638.2591.45.camel@x61.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    --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

all inboxes | Powered by JetHome®