From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dongsheng Song <dongsheng.song@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: Re: [PATCH] arch/x86/xen: remove depends on CONFIG_EXPERIMENTAL
Date: Sun, 24 Feb 2013 06:40:17 -0800 [thread overview]
Message-ID: <20130224144017.GB1111@kroah.com> (raw)
In-Reply-To: <CAE8XmWq+dA5Pvhyoxm2Nqbt0psLpPxUdR7i5MKFhxVxubY0QtQ@mail.gmail.com>
On Sun, Feb 24, 2013 at 05:51:44PM +0800, Dongsheng Song wrote:
> On Sun, Feb 24, 2013 at 1:03 AM, Kees Cook <keescook@chromium.org> wrote:
> > On Sat, Feb 23, 2013 at 3:59 AM, Dongsheng Song
> > <dongsheng.song@gmail.com> wrote:
> >> On Sat, Feb 23, 2013 at 3:29 PM, Kees Cook <keescook@chromium.org> wrote:
> >>>
> >>> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
> >>> while now and is almost always enabled by default. As agreed during the
> >>> Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
> >>>
> >>> Signed-off-by: Kees Cook <keescook@chromium.org>
> >>> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> >>> Cc: Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >>> ---
> >>> arch/x86/xen/Kconfig | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
> >>> index 93ff4e1..8cada4c 100644
> >>> --- a/arch/x86/xen/Kconfig
> >>> +++ b/arch/x86/xen/Kconfig
> >>> @@ -53,7 +53,7 @@ config XEN_DEBUG_FS
> >>>
> >>> config XEN_X86_PVH
> >>> bool "Support for running as a PVH guest (EXPERIMENTAL)"
> >>
> >> Why not remove this 'EXPERIMENTAL' too ?
> >
> > It was unclear to me if the feature was actually considered unstable.
> > I can resend with the text removed from the title too, if that's the
> > correct action here?
> >
> > -Kees
> >
>
> If such a feature was considered unstable, it should depends on EXPERIMENTAL.
CONFIG_EXPERIMENTAL is going away.
> We should not surprised users.
You should not have unstable options in the kernel in the first place,
sorry.
greg k-h
next prev parent reply other threads:[~2013-02-24 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 7:29 Kees Cook
2013-02-23 11:59 ` Dongsheng Song
2013-02-23 17:03 ` Kees Cook
2013-02-23 19:11 ` Konrad Rzeszutek Wilk
2013-02-23 20:47 ` Stefano Stabellini
2013-02-25 9:25 ` [Xen-devel] " Ian Campbell
2013-02-25 11:57 ` Stefano Stabellini
2013-02-24 9:51 ` Dongsheng Song
2013-02-24 14:40 ` Greg Kroah-Hartman [this message]
2013-02-25 12:39 ` Stefano Stabellini
2013-02-25 12:55 ` Konrad Rzeszutek Wilk
2013-02-25 14:37 ` Greg Kroah-Hartman
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=20130224144017.GB1111@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dongsheng.song@gmail.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=keescook@chromium.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mukesh.rathor@oracle.com \
--cc=stefano.stabellini@eu.citrix.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
Powered by JetHome