[linux-next] Adding keystone kernel tree
santosh.shilimkar at ti.com
Tue Feb 18 11:38:51 EST 2014
On Monday 17 February 2014 06:46 PM, Stephen Rothwell wrote:
> Hi Santosh,
> On Mon, 17 Feb 2014 17:23:17 -0500 Santosh Shilimkar <santosh.shilimkar at ti.com> wrote:
>> I would like to add keystone-linux next to linux-next to take advantage
>> of testing and integration issues. The tree is already officially
>> mentioned in the MAINTAINERS file
>> ARM/TEXAS INSTRUMENT KEYSTONE ARCHITECTURE
>> M: Santosh Shilimkar <santosh.shilimkar at ti.com>
>> L: linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
>> S: Maintained
>> F: arch/arm/mach-keystone/
>> F: drivers/clk/keystone/
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
>> Can you please add 'next' branch from the git tree to linux-next ?
> Added from today. I assume that it will be merged via the arm-soc tree?
> 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
> * submitted under GPL v2 (or later) and include the Contributor's
> * 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.
More information about the linux-arm-kernel