Message-ID: <555E5602.7020801@broadcom.com>
Date: Thu, 21 May 2015 15:02:42 -0700
From: Ray Jui <rjui@broadcom.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Florian Fainelli <f.fainelli@gmail.com>,
        Kishon Vijay Abraham I <kishon@ti.com>
CC: <linux-kernel@vger.kernel.org>,
        "JD (Jiandong) Zheng" <jdzheng@broadcom.com>,
        Arun Parameswaran <arunp@broadcom.com>,
        <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support
References: <1432085014-20758-1-git-send-email-rjui@broadcom.com> <1432085014-20758-3-git-send-email-rjui@broadcom.com> <555DD9D5.3000206@ti.com> <555E4F8F.9050503@broadcom.com> <555E5360.6090202@gmail.com>
In-Reply-To: <555E5360.6090202@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1683
Lines: 40


On 5/21/2015 2:51 PM, Florian Fainelli wrote:
> On 21/05/15 14:35, Ray Jui wrote:
>> 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?
> 
> In the case of drivers/bus/brcmstb_gisb.c I sent change via an arm-soc
> pull request relating to driver/SoC code changes, and Arnd merged these
> changes the same way he did merge changes for code in arch/arm/
> 

Thanks for the tip, Florian!

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