arm-soc tree inclusion
From: Stephen Rothwell
Date: Sat Jul 16 2011 - 00:01:30 EST
On Thu, 7 Jul 2011 13:05:01 +0200 Arnd Bergmann <arnd@xxxxxxxx> wrote:
> Ok, I guess that means you also won't be able to merge the arm-soc tree
> before the merge window, right?
> I meant to ask you to include the master branch of
> but we first had to move it into the right location. Can you add
> that when you get back?
I will add this tree in the next linux-next release.
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.
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
Description: PGP signature