Apply for adding my tree for linux-next
A message that is not in the archive (sent off-list or not yet received): 20151022025150.GA16895@shlinux2
Hi Peter,
Quoted 8 lines · On Thu, 22 Oct 2015 10:51:51 +0800 Peter Chen <[email protected]> wrote:
Would you please help adding my tree for linux-next tree, currently it is mainly for usb chipidea driver, later it will include USB OTG stuff.
Tree:
git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.git
Quoted 7 lines
Fix stuff
Name: usb-chipidea-fixes
branch name: ci-for-usb-stableNext stuff
Name: usb-chipidea-next
branch name: ci-for-usb-next
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 · 3 lines
Cheers, Stephen Rothwell [email protected]
Quoted 35 lines · Stephen Rothwell
Hi Peter,
Quoted 8 lines · On Thu, 22 Oct 2015 10:51:51 +0800 Peter Chen <[email protected]> wrote:
Would you please help adding my tree for linux-next tree, currently it is mainly for usb chipidea driver, later it will include USB OTG stuff.
Tree:
git://git.kernel.org/pub/scm/linux/kernel/git/peter.chen/usb.gitQuoted 7 lines
Fix stuff
Name: usb-chipidea-fixes
branch name: ci-for-usb-stableNext stuff
Name: usb-chipidea-next
branch name: ci-for-usb-nextAdded 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.
Quoted 3 lines
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.
I see, thanks.
Signature · 2 lines
Best Regards, Peter Chen