From: Paul Bolle <pebolle@tiscali.nl>
To: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Matt Wilson <msw@amazon.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Michael Opdenacker <michael.opdenacker@free-electrons.com>,
jeremy@goop.org, xen-devel@lists.xensource.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, mingo@redhat.com,
tglx@linutronix.de
Subject: Re: [Xen-devel] [PATCH] xen: remove unused Kconfig parameter
Date: Tue, 09 Jul 2013 01:35:34 +0200 [thread overview]
Message-ID: <1373326534.1438.10.camel@x61.thuisdomein> (raw)
In-Reply-To: <20130708205834.GA481@pd.tnic>
On Mon, 2013-07-08 at 22:58 +0200, Borislav Petkov wrote:
> On Mon, Jul 08, 2013 at 01:29:40PM -0700, H. Peter Anvin wrote:
> > What. The. Fuck.
>
> This is just marvellous: grub2 has a bunch of scripts in /etc/grub.d
> which rely on the presence of kernel config files in /boot or / and
> greps them in order to do the menu entries based on the built-in
> features it finds in them.
0) I've raised this issue a few months ago, but not on the LKML (see
http://thread.gmane.org/gmane.linux.kernel.virtualization/19126 ).
1) And I also asked whether "userspace [can] require the build system to
keep using some Kconfig symbol" (see
http://article.gmane.org/gmane.linux.kernel.virtualization/19129 ).
Peter and you clearly think userspace can't.
2) But anyhow, unless that grub2 configuration file has changed, this
Kconfig symbol can still be dropped, because grub2's check for it is
actually superfluous.
Paul Bolle
next prev parent reply other threads:[~2013-07-08 23:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 6:28 Michael Opdenacker
2013-07-08 19:28 ` Konrad Rzeszutek Wilk
2013-07-08 19:34 ` [Xen-devel] " Matt Wilson
2013-07-08 20:29 ` H. Peter Anvin
2013-07-08 20:58 ` Borislav Petkov
2013-07-08 23:35 ` Paul Bolle [this message]
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
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
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 20:13 ` H. Peter Anvin
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=1373326534.1438.10.camel@x61.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.opdenacker@free-electrons.com \
--cc=mingo@redhat.com \
--cc=msw@amazon.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
all inboxes | Powered by JetHome®