linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: Apply for adding my tree for linux-next
       [not found] <20151022025150.GA16895@shlinux2>
@ 2015-10-31 22:25 ` Stephen Rothwell
  2015-11-02  9:44   ` Peter Chen
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2015-10-31 22:25 UTC (permalink / raw)
  To: Peter Chen, linux-next; +Cc: Greg KH

Hi Peter,

On Thu, 22 Oct 2015 10:51:51 +0800 Peter Chen <peter.chen@freescale.com> 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
> 
> Fix stuff 
> Name: usb-chipidea-fixes
> branch name: ci-for-usb-stable
> 
> Next 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.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Apply for adding my tree for linux-next
  2015-10-31 22:25 ` Apply for adding my tree for linux-next Stephen Rothwell
@ 2015-11-02  9:44   ` Peter Chen
  0 siblings, 0 replies; 2+ messages in thread
From: Peter Chen @ 2015-11-02  9:44 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, Greg KH

On Sun, Nov 01, 2015 at 09:25:46AM +1100, Stephen Rothwell wrote:
> Hi Peter,
> 
> On Thu, 22 Oct 2015 10:51:51 +0800 Peter Chen <peter.chen@freescale.com> 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
> > 
> > Fix stuff 
> > Name: usb-chipidea-fixes
> > branch name: ci-for-usb-stable
> > 
> > Next 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.
> 

I see, thanks.

-- 

Best Regards,
Peter Chen

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-11-02  9:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20151022025150.GA16895@shlinux2>
2015-10-31 22:25 ` Apply for adding my tree for linux-next Stephen Rothwell
2015-11-02  9:44   ` Peter Chen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).