Re: linux-next: add the omap-pending tree

[Stephen Rothwell <sfr@canb.auug.org.au>]

[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]

Hi Paul,

On Fri, 19 Dec 2014 19:28:08 +0000 (UTC) Paul Walmsley <paul@pwsan.com> wrote:
>
> Might you be willing to include this branch in your linux-next builds?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git#for-next
> 
> It will include OMAP clock, bus architecture, and low-level power 
> management patches that are planned to be included in pull requests to the 
> OMAP upstream maintainer, Tony Lindgren.  He in turn will submit pull 
> requests to the arm-soc tree.  The objective in including this branch is 
> to get these patches integration-tested earlier than they would be 
> otherwise.

Added from today (called "omap" and with you as the contact).

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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]