All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@freescale.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: Apply for adding my tree for linux-next
Date: Mon, 2 Nov 2015 17:44:56 +0800	[thread overview]
Message-ID: <20151102094455.GC5464@shlinux2> (raw)
In-Reply-To: <20151101092546.093cddfe@canb.auug.org.au>

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

      reply	other threads:[~2015-11-02  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151102094455.GC5464@shlinux2 \
    --to=peter.chen@freescale.com \
    --cc=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.