public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@linux.ie>
Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm request 2
Date: Tue, 2 Mar 2010 15:06:17 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003021505000.3616@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.1003022300320.4099@skynet.skynet.ie>



On Tue, 2 Mar 2010, Dave Airlie wrote:
> 
> because it does nothing on anything except the laptops in question and on 
> those it does nothing except add a control file in debugfs?

It's still code. And if the user didn't ask for it, it should damn well 
not be there.

> So how am I supposed to indicate to distro vendors that something should 
> be turned on? If you think that distro kernel maintainers really 
> understand every config option that goes past, I've got a bridge.

User configurations is _not_ your job. Your job is to make sure that the 
kernel works, and people who don't ask for new feaures don't get them.

		Linus

  reply	other threads:[~2010-03-02 23:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 23:46 [git pull] drm request 2 Dave Airlie
2010-03-02 22:59 ` Linus Torvalds
2010-03-02 23:02   ` Dave Airlie
2010-03-02 23:06     ` Linus Torvalds [this message]
2010-03-02 23:09       ` Linus Torvalds
2010-03-03 11:12     ` Thomas Backlund
2010-03-02 23:03   ` Linus Torvalds
2010-03-02 23:16     ` Dave Airlie
2010-03-02 23:27       ` Dave Airlie
2010-03-02 23:40         ` Linus Torvalds
2010-03-02 23:48           ` Dave Airlie
2010-03-03  0:34             ` Linus Torvalds

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.1003021505000.3616@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.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