Hi Heiko,
On Fri, 21 Aug 2015 11:25:12 +0200 Heiko Stuebner <heiko at sntech.de> wrote:
>
> not sure if there is some expected protocol to follow for linux-next
> inclusions (basic search didn't turn up anything of that type).
>
> Anyway, could you include the following tree into linux-next please?
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
> branch for-next
>
> It looks like some kernelci people want to do testing a bit earlier than my
> pulls to arm-soc, so it would be nice to have rockchip-specific changes in
> next.
Added from today.
You may need to be a bit more careful about Signed-off-by lines - for
example, commit cb8cc37f4d38 ("ARM: rockchip: fix broken build") has no
Signed-off-by from its author.
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 at canb.auug.org.au
