[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150410094914.4c855142@canb.auug.org.au>
Date: Fri, 10 Apr 2015 09:49:14 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Rob Clark <robdclark@...il.com>
Cc: Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
linux-next@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Hai Li <hali@...eaurora.org>, Dave Airlie <airlied@...ux.ie>,
Bjorn Andersson <bjorn.andersson@...ymobile.com>
Subject: drm-msm tree (Was: Re: linux-next: build failure after merge of the
regulator tree)
Hi Rob,
On Thu, 9 Apr 2015 11:00:44 -0400 Rob Clark <robdclark@...il.com> wrote:
>
> Thanks.. btw, would it be possible to get my msm-next branch picked up
> by linux-next? That seems like it would help to catch these earlier..
>
> git://people.freedesktop.org/~robclark/linux msm-next
Added from today.
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@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists