Prev: [PATCH] Make sure abs() works as expected with both ints and longs
Next: Regression 2.6.35-rc6: ALSA Intel HDA/Realtek: missing Beep
From: Stephen Rothwell on 28 Jul 2010 11:40
On Wed, 28 Jul 2010 15:50:55 +0200 Tejun Heo <tj(a)kernel.org> wrote:
> If possible, can you please pull the following branch into linux-next?
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git lost-spurious-irq
> It's scheduled to go through tip/genirq, so once it shows up in tip,
> the above branch can be dropped from linux-next. As the merge window
> is closing in, I'm hoping to get it tested enough in linux-next. The
> branch is based on rc3 but merges without conflict into the current
OK, added from today. I'll keep an eye out for it in the tip tree.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
* submitted under GPL v2 (or later) and include the Contributor's
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.