From: Tero Kristo <t-kristo@ti.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
David Miller <davem@davemloft.net>
Cc: <m-karicheri2@ti.com>, <nsekhar@ti.com>, <robh+dt@kernel.org>,
<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [for-next PATCH v2 0/5] phy: ti: gmii-sel: add support for am654x/j721e soc
Date: Fri, 20 Mar 2020 11:08:41 +0200 [thread overview]
Message-ID: <a6fad5b9-fb90-2db7-9876-d875a91b0633@ti.com> (raw)
In-Reply-To: <7c5395a6-56cb-1d2a-0243-99a6b0fed2a7@ti.com>
On 05/03/2020 12:55, Grygorii Strashko wrote:
>
>
> On 05/03/2020 07:17, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On 05/03/20 4:09 am, David Miller wrote:
>>> From: Grygorii Strashko <grygorii.strashko@ti.com>
>>> Date: Tue, 3 Mar 2020 18:00:24 +0200
>>>
>>>> Hi Kishon,
>>>>
>>>> This series adds support for TI K3 AM654x/J721E SoCs in TI
>>>> phy-gmii-sel PHY
>>>> driver, which is required for future adding networking support.
>>>>
>>>> depends on:
>>>> [PATCH 0/2] phy: ti: gmii-sel: two fixes
>>>> https://lkml.org/lkml/2020/2/14/2510
>>>>
>>>> Changes in v2:
>>>> - fixed comments
>>>>
>>>> v1: https://lkml.org/lkml/2020/2/22/100
>>>
>>> This is mostly DT updates and not much networking code changes, will
>>> some other
>>> tree take this?
>>
>> I can take the phy related changes. Grygorii, can you split the dt
>> patches into a separate series?
>
> sure. Could pls, pick up 1-3 and I'll resend 4-5.
> Or you want me re-send once again?
>
Queued up patches #4 and #5 towards 5.7, thanks.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2020-03-20 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 16:00 [for-next PATCH v2 0/5] phy: ti: gmii-sel: add support for am654x/j721e soc Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 1/5] phy: ti: gmii-sel: simplify config dependencies between net drivers and gmii phy Grygorii Strashko
2020-03-05 11:06 ` Kishon Vijay Abraham I
2020-03-13 15:07 ` Grygorii Strashko
[not found] ` <20200316140859.GA30922@a0393678ub>
2020-03-16 21:16 ` Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 2/5] dt-bindings: phy: ti: gmii-sel: add support for am654x/j721e soc Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 3/5] " Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 4/5] arm64: dts: ti: k3-am65-mcu: add phy-gmii-sel node Grygorii Strashko
2020-03-03 16:00 ` [for-next PATCH v2 5/5] arm64: dts: ti: k3-j721e-mcu: add scm node and phy-gmii-sel nodes Grygorii Strashko
2020-03-04 22:39 ` [for-next PATCH v2 0/5] phy: ti: gmii-sel: add support for am654x/j721e soc David Miller
2020-03-05 5:17 ` Kishon Vijay Abraham I
2020-03-05 10:55 ` Grygorii Strashko
2020-03-20 9:08 ` Tero Kristo [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=a6fad5b9-fb90-2db7-9876-d875a91b0633@ti.com \
--to=t-kristo@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
/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 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).