Please add imx-drm/next and etnaviv/next to linux-next

Please add imx-drm/next and etnaviv/next to linux-next

[Lucas Stach]

Hi Stephen,

can you please add imx-drm/next and etnaviv/next to the linux-next tree?

Both trees stage patches which will eventually feed into Dave Airlie's
drm-next tree.

https://git.pengutronix.de/git/pza/linux imx-drm/next

https://git.pengutronix.de/git/lst/linux etnaviv/next

Regards,
Lucas

Re: Please add imx-drm/next and etnaviv/next to linux-next

[Stephen Rothwell]

Hi Lucas,

On Wed, 12 Apr 2017 15:59:44 +0200 Lucas Stach <l.stach@pengutronix.de> wrote:
>
> can you please add imx-drm/next and etnaviv/next to the linux-next tree?
> 
> Both trees stage patches which will eventually feed into Dave Airlie's
> drm-next tree.
> 
> https://git.pengutronix.de/git/pza/linux imx-drm/next
> 
> https://git.pengutronix.de/git/lst/linux etnaviv/next

Added from tomorrow with just you as contact.  Let me know if there
should be other contacts.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement 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