From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: [git pull] drm patches for 2.6.27 final
Date: Sun, 24 Aug 2008 10:16:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808241013510.3363@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.0.82.0808240809170.15834@skynet.skynet.ie>
On Sun, 24 Aug 2008, Dave Airlie wrote:
>
> So this has fixes for the SiS build with fbdev, a fix for a warning
> reported by Jiri Slaby in the irq locking code, a fix for debugging the X
> server startup sequence, r300/r500 radeon lockup fixes, Intel hw
> instability fixes in the irq and hw status pages, and the biggest
> bit is a fix for the backlight keys on a bunch of Intel laptops which is
> enabled using opregion support from Matthew Garrett.
Quite frankly, I'm not going to take this.
None of what you describe sounds like regressions, and this is just TOO
F*CKING LATE to take big changes like this, to a fragile subsystem that
has historically easily introduced new regressions.
Can you please make a branch with ONLY REGRESSIONS, or fixes for major
problems that don't introduce several thousand lines of new code?
Because you seem to be constantly unable to understand what "merge window"
means. And I'm not going to take this kind of crap.
Linus
next prev parent reply other threads:[~2008-08-24 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-24 7:18 Dave Airlie
2008-08-24 17:16 ` Linus Torvalds [this message]
2008-08-24 20:57 ` Dave Airlie
2008-08-25 6:49 ` Peter Zijlstra
2008-08-25 7:57 ` Peter Zijlstra
2008-08-25 8:03 ` 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.1.10.0808241013510.3363@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®