From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [GIT PULL] x86 platform driver updates for 2.6.35-rc3
Date: Tue, 8 Jun 2010 18:10:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1006081806040.4506@i5.linux-foundation.org> (raw)
In-Reply-To: <20100608221901.GA25294@srcf.ucam.org>
On Tue, 8 Jun 2010, Matthew Garrett wrote:
>
> Some fixes for error paths, some config fixes, a minor update to hp-wmi
> that deals with some annoying corner cases like AC adapter events being
> interpreted as brightness down keystrokes and the Intel IPS driver. This
> requires a small addition to the timer API but doesn't modify any
> existing code. Should all be entirely low impact.
[ Very shortly after sending out an email about how most developers
probably don't end up reading much of lkml, and thus having missed all
the other threads on this subject ]
Everybody repeat after me: "After -rc2 I won't be taking patches or pull
requests that aren't regression fixes or fixes to major bugs (oopses or
security etc)".
See the -rc2 announcement, or any of (by now) roughly ten different
threads on lkml and a couple of other mailing lists as response to pull
requests etc ;^)
And yes, that very much does include new drivers. Especially if they end
up affecting anything else (but in al honesty, I probably wouldn't take it
now even if it was entirely standalone).
Linus
next prev parent reply other threads:[~2010-06-09 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 22:19 Matthew Garrett
2010-06-09 1:10 ` Linus Torvalds [this message]
2010-06-09 1:24 ` Jesse Barnes
2010-06-09 1:57 ` Linus Torvalds
2010-06-09 2:03 ` Dave Airlie
2010-06-09 16:31 ` Jesse Barnes
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.1006081806040.4506@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@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
Powered by JetHome