mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: Dave Airlie <airlied@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kms in defconfig
Date: Mon, 27 Apr 2009 18:59:01 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904271852510.22156@localhost.localdomain> (raw)
In-Reply-To: <49F65FA2.4010603@kernel.org>



On Tue, 28 Apr 2009, Tejun Heo wrote:
> 
> I think defconfig should enable options such that it shows where
> upstream kernel is headed, so FWIW +1 for KMS from me.

I'd actually love to get rid of the stupid defconfig's entirely. They've 
lost pretty much all relevance over the years, except for specific cases 
where you might have defconfigs that are for specific platforms.

IOW, the embedded kind of "per-platform defconfig" at lest is a useful 
starting point. But even there I'm not 100% sure that it makes sense to 
pollute the kernel source tree with them - they mess up things like

	git grep PREVENT_FIRMWARE_BUILD

horribly.

IOW, they're likely to be more pain than they are worth. And they really 
aren't useful starting points for normal people (who are probably better 
off starting with their distro kernel config) or likely even for most 
kernel developers (who hopefully have noticed that they can install a 
per-machine defconfig in /etc/kernel-config and forget about it).

I'd love to just delete them all.

			Linus

  reply	other threads:[~2009-04-28  2:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27  8:21 Dave Airlie
2009-04-27  8:39 ` Ingo Molnar
2009-04-27  8:56   ` Dave Airlie
2009-04-28  1:45     ` Tejun Heo
2009-04-28  1:59       ` Linus Torvalds [this message]
2009-04-28  6:29         ` Ingo Molnar
2009-04-28 16:54         ` david
2009-04-28 17:13           ` Linus Torvalds
2009-04-28 17:22             ` Ingo Molnar
2009-04-28 17:36               ` Steven Rostedt
2009-04-28 19:18                 ` Ingo Molnar
2009-04-28 21:23                   ` Steven Rostedt
2009-04-28 17:23             ` david
2009-04-28 17:50               ` Linus Torvalds
2009-04-28 21:43                 ` Florian Mickler
2009-04-28 21:50                   ` david
2009-04-28 23:10                     ` Florian Mickler
2009-04-28 23:29                       ` david
2009-04-29  6:55                   ` Giacomo Catenazzi
2009-04-29  5:36     ` Andrew Morton
2009-04-29  5:59       ` Dave Airlie
2009-04-27 15:40   ` Peter Zijlstra
2009-04-28  1:54     ` Dave Airlie
2009-04-28  7:32       ` Peter Zijlstra
2009-04-28 17:04         ` Jesse Barnes
2009-04-28 23:42         ` Dave Airlie

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=alpine.LFD.2.00.0904271852510.22156@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@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

all inboxes | Powered by JetHome®