Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964806AbbEUVv6 (ORCPT ); Thu, 21 May 2015 17:51:58 -0400 Received: from mail-pa0-f50.google.com ([209.85.220.50]:35064 "EHLO mail-pa0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755163AbbEUVv5 (ORCPT ); Thu, 21 May 2015 17:51:57 -0400 Message-ID: <555E5360.6090202@gmail.com> Date: Thu, 21 May 2015 14:51:28 -0700 From: Florian Fainelli User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Ray Jui , Kishon Vijay Abraham I CC: linux-kernel@vger.kernel.org, "JD (Jiandong) Zheng" , Arun Parameswaran , 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> In-Reply-To: <555E4F8F.9050503@broadcom.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1579 Lines: 34 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/ -- Florian -- 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/