public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Backlund <tmb@mandriva.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm request 2
Date: Wed, 03 Mar 2010 13:12:31 +0200	[thread overview]
Message-ID: <4B8E441F.5090701@mandriva.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003022300320.4099@skynet.skynet.ie>

03.03.2010 01:02, Dave Airlie skrev:
>>> x86 after PPC (I think I just validated Ingo).
>>
>> Why is VGA_SWITCHEROO enabled by default?
>
> because it does nothing on anything except the laptops in question and on
> those it does nothing except add a control file in debugfs?
>
> 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.
>

Yep. If the help-text for a new config option is well written, a kernel 
maintainer will have no problem deciding what to do.
(the help text for the config in question is wery well written, thanks
  to whoever wrote that)

And this specific option/feature is already requested by endusers, so no
maintainer will be able to "miss it" :-)

--
Thomas

  parent reply	other threads:[~2010-03-03 11:12 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
2010-03-02 23:09       ` Linus Torvalds
2010-03-03 11:12     ` Thomas Backlund [this message]
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=4B8E441F.5090701@mandriva.org \
    --to=tmb@mandriva.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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