Request for Inclusion in linux-next
Hi Stephen,
Would it be possible to add the sunxi tree for linux-next coverage.
git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git, branch sunxi/for-next
It will be based on Linus' tree.
Thanks,
Maxime
Signature · 10 lines
Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140623/4a974a29/attachment.sig>
Hi Maxime,
Quoted 6 lines · On Mon, 23 Jun 2014 23:15:00 +0200 Maxime Ripard…
Would it be possible to add the sunxi tree for linux-next coverage.
git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git, branch sunxi/for-nextIt will be based on Linus' tree.
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.
Signature · 10 lines
Cheers, Stephen Rothwell sfr at canb.auug.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140624/35295dc0/attachment.sig>