* Re: new branch for linux-next (irqchip)
[not found] <20140513160537.GD27822@titan.lakedaemon.net>
@ 2014-05-14 0:10 ` Stephen Rothwell
0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2014-05-14 0:10 UTC (permalink / raw)
To: Jason Cooper; +Cc: Thomas Gleixner, linux-next
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Hi Jason,
On Tue, 13 May 2014 12:05:37 -0400 Jason Cooper <jason@lakedaemon•net> wrote:
>
> Thomas has recently asked me to lend him a hand reviewing and
> collecting patches for drivers/irqchip. I'll then send him a pull
> request for that branch. So, it's very similar to what we (mvebu) does
> wrt arm-soc.
>
> If you could please add the following branch to your list, we'd
> appreciate it.
>
> Contact: Jason Cooper <jason@lakedaemon•net>
> ML: linux-kernel@vger•kernel.org
> Tree: git://git.infradead.org/users/jcooper/linux.git
> Branch: irqchip/for-next
Added from today. I note that the branch is currently empty (which is
fine - just checking).
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
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* 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.
--
Cheers,
Stephen Rothwell
sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] only message in thread