From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>,
dri-devel@lists.sf.net, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [git pull] drm request 2
Date: Tue, 2 Mar 2010 16:34:03 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1003021630250.3616@localhost.localdomain> (raw)
In-Reply-To: <21d7e9971003021548u7509651fyfc875d4e30472486@mail.gmail.com>
On Wed, 3 Mar 2010, Dave Airlie wrote:
>
> So can we get linux-next builds to build with *your* Kconfig? This should
> cut down the amount of crap you see considerably.
No.
Dave, _think_ about what you're saying.
The absolute last thing we want to do is to make it easier for crap to
flow through the system.
We don't want to make it easier to hide problems.
I think we might want to instead extend on the tests that linux-next does.
For example, STAGING should generally always compile.
There are exceptions - major "change the world" changes where staging
drivers might not be updated in as timely a manner as other drivers, but
they should be exceptions, not the rule.
If a driver really doesn't even compile, it should be marked BROKEN, not
STAGING.
Linus
prev parent reply other threads:[~2010-03-03 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 23:46 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
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 [this message]
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.1003021630250.3616@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®