linux-kernel - Re: [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 May 2015 14:35:11 -0700
From:	Ray Jui <rjui@...adcom.com>
To:	Kishon Vijay Abraham I <kishon@...com>
CC:	<linux-kernel@...r.kernel.org>,
	"JD (Jiandong) Zheng" <jdzheng@...adcom.com>,
	Arun Parameswaran <arunp@...adcom.com>,
	<bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support

On 5/21/2015 6:12 AM, Kishon Vijay Abraham I wrote:
> Hi,
> 
> On Wednesday 20 May 2015 06:53 AM, Ray Jui wrote:
>> This adds the support for the iProc MDC/MDIO interface. Multiple iProc
>> SoCs contain the MDC/MDIO interface that can be used for the host to
>> communicate with various Serdes/PHYs including Ethernet, PCIe, USB, etc.
> 
> the term phy used in this driver is misleading. It's not a PHY actually.
> This sounds more like a bus driver to me and should be present in
> drivers/bus?

Sure I can move it to drivers/bus/* if that's more appropriate.
Typically MDIO is used with Ethernet PHYs and most people register it to
the mii bus under drivers/net/ethernet. Our case is rare, where the same
MDIO interface is shared by the Ethernet PHY and other types of PHYs.
But yeah that does not change the fact that this is more of a bus type
of driver than a PHY driver.

I checked the maintainers' list and found apparently there's no
maintainer for drivers/bus/*? In this case, who is supposed to ack and
send a pull request for the patch?

Thanks,

Ray
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/