[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160426.122624.967268334782802268.davem@davemloft.net>
Date: Tue, 26 Apr 2016 12:26:24 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: andrew@...n.ch
Cc: pramod.kumar@...adcom.com, robh+dt@...nel.org,
catalin.marinas@....com, will.deacon@....com,
yamada.masahiro@...ionext.com, wens@...e.org, mark.rutland@....com,
devicetree@...r.kernel.org, pawel.moll@....com, arnd@...db.de,
suzuki.poulose@....com, netdev@...r.kernel.org,
punit.agrawal@....com, linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org, anup.patel@...adcom.com
Subject: Re: [PATCH 1/6] bus: Add shared MDIO bus framework
From: Andrew Lunn <andrew@...n.ch>
Date: Tue, 26 Apr 2016 14:13:35 +0200
> On Tue, Apr 26, 2016 at 02:03:27PM +0530, Pramod Kumar wrote:
>> As you can see from above points, trying to re-use Linux Ethernet MDIO mux
>> framework for non-Ethernet PHYs is not the right way.
>
> And as i pointed out, all your arguments are wrong, bar one. And i
> doubt that one argument is sufficient to duplicate a lot of code which
> already exists and does 95% of what you need.
+1
Powered by blists - more mailing lists