* Re: Resurrecting linux-next tree for Xtensa
2012-08-09 3:24 Resurrecting linux-next tree for Xtensa Chris Zankel
@ 2012-08-09 22:53 ` Stephen Rothwell
2012-08-09 23:04 ` Chris Zankel
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Rothwell @ 2012-08-09 22:53 UTC (permalink / raw)
To: Chris Zankel; +Cc: linux-next, Max Filippov
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
Hi Chris.
On Wed, 08 Aug 2012 20:24:07 -0700 Chris Zankel <chris@zankel.net> wrote:
>
> I was wondering and hoping you could add the Xtensa 'next' tree back to
> the linux-next tree?
>
> It's currently on github (at least, until I get my access back to
> kernel.org)
You will need to get a gpg key signed so that you can move this tree to
kernel.org or to signed tags when you ask Linus to pull your tree.
> git://github.com/czankel/xtensa-linux.git#for-next
^
I used "for_next". Just to be sure, that branch is currently empty,
right?
> It's been outdated for some time now and with more help we want to bring
> it up-to-date again.
Sounds like a good plan!
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@canb.auug.org.au
Legal Stuff:
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.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread