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

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

Hi,

On Friday 21 October 2016 03:30 AM, Stephen Rothwell wrote:
> 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?

I send pull request to gregkh. This tree contains USB, SATA and other PHYs
except ethernet PHY. greg generally merges it into his USB tree.
> 
> 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,

hmm.. I see atleast 4 drivers in drivers/phy which has just
MODULE_LICENSE("GPL"). I can check if these can be changed to GPL v2.
>      * 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.

sure, I understand and agree to all of this.

Thanks
Kishon

next prev parent reply	other threads:[~2016-10-21  4:39 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 ` including PHY tree in linux-next Stephen Rothwell
2016-10-21  4:39   ` Kishon Vijay Abraham I [this message]
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=58099C11.8050700@ti.com \
    --to=kishon@ti$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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