public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: John Stoffel <john@stoffel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	Austin S Hemmelgarn <ahferroin7@gmail.com>,
	Brian Gerst <brgerst@gmail.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] x86/kconfig/32: Make CONFIG_VM86 default to n and remove EXPERT
Date: Fri, 10 Jul 2015 15:41:41 +0200	[thread overview]
Message-ID: <20150710134140.GA27233@amd> (raw)
In-Reply-To: <21918.52899.989624.140180@quad.stoffel.home>

On Thu 2015-07-09 15:42:27, John Stoffel wrote:
> >>>>> "Linus" == Linus Torvalds <torvalds@linux-foundation.org> writes:
> 
> Linus> On Thu, Jul 9, 2015 at 11:51 AM, Arjan van de Ven <arjan@linux.intel.com> wrote:
> >> 
> >> I would rather do BOTH the default n AND the EXPERT
> 
> Linus> That basically makes it impossible for "normal people" to test it. You
> Linus> have to mark yourself as expert, and then get the rest of the
> Linus> configuration right. Not a good idea.
> 
> Linus> The kernel config is probably our biggest problem for getting
> Linus> people to test. Building the kernel? Easy. Installing it? "make
> Linus> install; make modules_install". Not that hard, unless your
> Linus> distro has screwed it up (which has happened, I'm looking at
> Linus> you, Ubuntu).
> 
> The big problem with the kernel config is the piles and piles of crap
> which makes finding the common cases really really hard, and I've been
> following this list and building kernels off and on now for 12+
> years.

And you are lucky not to work on embedded stuff.

If I lost configs for n900, I'd probably not be able to come with
something working...

Given that we already have device trees... it would be nice to
separate real config *options* (like do you want penguin logo on
console? How big font?) from options you need to get right to get
useful hardware configuration, and parse the later ones from dts..

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2015-07-10 13:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 18:40 [PATCH] x86/kconfig/32: Make CONFIG_VM86 default to n and remove EXPERT Andy Lutomirski
2015-07-09 18:43 ` Kees Cook
2015-07-09 18:51 ` Arjan van de Ven
2015-07-09 19:00   ` Andy Lutomirski
2015-07-09 19:20   ` Linus Torvalds
2015-07-09 19:42     ` John Stoffel
2015-07-10 13:41       ` Pavel Machek [this message]
2015-07-10  8:45     ` Ingo Molnar
2015-07-09 19:27 ` Yuhong Bao

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=20150710134140.GA27233@amd \
    --to=pavel@ucw.cz \
    --cc=ahferroin7@gmail.com \
    --cc=arjan@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=john@stoffel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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