public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kishon Vijay Abraham I <kishon@ti•com>
Cc: linux-next@vger•kernel.org
Subject: Re: including PHY tree in linux-next
Date: Fri, 21 Oct 2016 09:00:41 +1100	[thread overview]
Message-ID: <20161021090041.46cc5fee@canb.auug.org.au> (raw)
In-Reply-To: <5808995C.3010300@ti.com>

Hi Kishon,

On Thu, 20 Oct 2016 15:45:56 +0530 Kishon Vijay Abraham I <kishon@ti•com> wrote:
>
> Can you include the following branches for linux-phy tree into linux-next?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next
> git://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git fixes

Added from today (called phy-next and phy respectively).  Will these be
merged via Dave Miller's trees, or directly to Linus?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement 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

next      parent reply	other threads:[~2016-10-20 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5808995C.3010300@ti.com>
2016-10-20 22:00 ` Stephen Rothwell [this message]
2016-10-21  4:39   ` including PHY tree in linux-next Kishon Vijay Abraham I
2016-10-23 22:27     ` Stephen Rothwell

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=20161021090041.46cc5fee@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=kishon@ti$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox