From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: jeremy@goop.org, xen-devel@lists.xensource.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, mingo@redhat.com,
hpa@zytor.com, tglx@linutronix.de
Subject: Re: [PATCH] xen: remove unused Kconfig parameter
Date: Mon, 8 Jul 2013 15:28:54 -0400 [thread overview]
Message-ID: <20130708192854.GF4927@phenom.dumpdata.com> (raw)
In-Reply-To: <1373264904-27053-1-git-send-email-michael.opdenacker@free-electrons.com>
On Mon, Jul 08, 2013 at 08:28:24AM +0200, Michael Opdenacker wrote:
> This patch proposes to remove the XEN_PRIVILEGED_GUEST kernel
> configuration parameter defined in arch/x86/xen/Kconfig, but used
> nowhere in the makefiles and source code.
>
> This dummy parameter was added 3 years back, and it may
> make sense to remove it now, as the reasons to use it were not
> very clear.
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Can't remove it. It is used by grub2.
> ---
> arch/x86/xen/Kconfig | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
> index 1a3c765..b6401dc 100644
> --- a/arch/x86/xen/Kconfig
> +++ b/arch/x86/xen/Kconfig
> @@ -19,11 +19,6 @@ config XEN_DOM0
> depends on XEN && PCI_XEN && SWIOTLB_XEN
> depends on X86_LOCAL_APIC && X86_IO_APIC && ACPI && PCI
>
> -# Dummy symbol since people have come to rely on the PRIVILEGED_GUEST
> -# name in tools.
> -config XEN_PRIVILEGED_GUEST
> - def_bool XEN_DOM0
> -
> config XEN_PVHVM
> def_bool y
> depends on XEN && PCI && X86_LOCAL_APIC
> --
> 1.8.1.2
>
next parent reply other threads:[~2013-07-08 19:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1373264904-27053-1-git-send-email-michael.opdenacker@free-electrons.com>
2013-07-08 19:28 ` Konrad Rzeszutek Wilk [this message]
2013-07-08 19:34 ` [Xen-devel] [PATCH] xen: remove unused Kconfig parameter Matt Wilson
2013-07-08 20:13 ` H. Peter Anvin
[not found] ` <20130708193457.GA6926@u109add4315675089e695.ant.amazon.com>
2013-07-08 20:29 ` [Xen-devel] " H. Peter Anvin
2013-07-08 20:58 ` Borislav Petkov
[not found] ` <20130708205834.GA481@pd.tnic>
2013-07-08 23:35 ` Paul Bolle
[not found] ` <1373326534.1438.10.camel@x61.thuisdomein>
2013-07-09 0:26 ` Konrad Rzeszutek Wilk
2013-07-09 7:41 ` Jan Beulich
2013-07-09 14:48 ` Konrad Rzeszutek Wilk
2013-07-09 14:54 ` Jan Beulich
2013-07-09 15:05 ` Borislav Petkov
[not found] ` <20130709150554.GA27579@pd.tnic>
2013-07-09 15:09 ` H. Peter Anvin
2013-07-09 17:19 ` Konrad Rzeszutek Wilk
2013-07-09 20:01 ` Borislav Petkov
2013-07-09 20:40 ` Konrad Rzeszutek Wilk
2013-07-09 20:57 ` Borislav Petkov
2013-07-09 22:34 ` Sander Eikelenboom
[not found] ` <1382658288.20130710003458@eikelenboom.it>
2013-07-10 3:20 ` Borislav Petkov
2013-07-10 3:55 ` H. Peter Anvin
2013-07-10 6:19 ` Matt Wilson
2013-07-10 7:41 ` Sander Eikelenboom
2013-07-10 14:46 ` Konrad Rzeszutek Wilk
2013-07-11 10:08 ` Paul Bolle
2013-07-11 17:57 ` H. Peter Anvin
2013-07-11 18:13 ` Paul Bolle
2013-07-11 18:24 ` Konrad Rzeszutek Wilk
2013-07-11 21:13 ` Geert Uytterhoeven
2013-07-08 6:28 Michael Opdenacker
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=20130708192854.GF4927@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--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 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).