linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Murali Karicheri <m-karicheri2@ti.com>,
	Tero Kristo <t-kristo@ti.com>,
	"David S . Miller" <davem@davemloft.net>,
	Sekhar Nori <nsekhar@ti.com>, Rob Herring <robh+dt@kernel.org>,
	netdev <netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [for-next PATCH v2 1/5] phy: ti: gmii-sel: simplify config dependencies between net drivers and gmii phy
Date: Mon, 16 Mar 2020 23:16:36 +0200	[thread overview]
Message-ID: <128961a1-8437-741d-96cc-ed24b790cabf@ti.com> (raw)
In-Reply-To: <20200316140859.GA30922@a0393678ub>



On 16/03/2020 16:08, Kishon Vijay Abraham I wrote:
> On Tue, Mar 03, 2020 at 06:00:25PM +0200, Grygorii Strashko wrote:
>> The phy-gmii-sel can be only auto selected in Kconfig and now the pretty
>> complex Kconfig dependencies are defined for phy-gmii-sel driver, which
>> also need to be updated every time phy-gmii-sel is re-used for any new
>> networking driver.
>>
>> Simplify Kconfig definition for phy-gmii-sel PHY driver - drop all
>> dependencies and from networking drivers and rely on using 'imply
>> PHY_TI_GMII_SEL' in Kconfig definitions for networking drivers instead.
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> 
> Acked-by: Kishon Vijay Abraham I <kishon@ti.com>

Thanks you, Kishon.

I'll include this patch in next version of my series to
add networking support for k3 am65x/j721e soc.

-- 
Best regards,
grygorii

  parent reply	other threads:[~2020-03-16 21:16 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 [this message]
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

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=128961a1-8437-741d-96cc-ed24b790cabf@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --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 \
    --cc=t-kristo@ti.com \
    /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).