Resurrecting linux-next tree for Xtensa
Hi Stephen,
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)
git://github.com/czankel/xtensa-linux.git#for-next
It's been outdated for some time now and with more help we want to bring it up-to-date again.
Thanks,
-Chris
Hi Chris.
Quoted 6 lines · On Wed, 08 Aug 2012 20:24:07 -0700 Chris Zankel <[email protected]> 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.
Quoted 1 line
git://github.com/czankel/xtensa-linux.git#for-next
^
I used "for_next". Just to be sure, that branch is currently empty, right?
Quoted 2 lines
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.
Signature · 15 lines
Cheers, Stephen Rothwell [email protected] 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.
Hi Stephen,
Quoted 10 lines · Stephen Rothwell
Hi Chris.
Quoted 5 lines · On Wed, 08 Aug 2012 20:24:07 -0700 Chris Zankel <[email protected]> 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.
Working on it...
Quoted 4 lines
Quoted 1 line
git://github.com/czankel/xtensa-linux.git#for-next^I used "
for_next". Just to be sure, that branch is currently empty, right?
Correct. Patches should be popping up in a few days...
Quoted 5 lines
Quoted 2 lines
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
I appreciate all the time and effort you put into the linux-next tree! Thanks so much!
Cheers!
-Chris