All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ray Jui <rjui@broadcom.com>
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
Date: Thu, 21 May 2015 15:02:42 -0700	[thread overview]
Message-ID: <555E5602.7020801@broadcom.com> (raw)
In-Reply-To: <555E5360.6090202@gmail.com>



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

  reply	other threads:[~2015-05-21 22:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  1:23 [PATCH 0/5] Add Cygnus PCIe PHY support Ray Jui
2015-05-20  1:23 ` [PATCH 1/5] phy: iproc-mdio: Define DT binding Ray Jui
2015-05-21 13:07   ` Kishon Vijay Abraham I
2015-05-21 21:29     ` Ray Jui
2015-05-20  1:23 ` [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support Ray Jui
2015-05-21  7:41   ` Paul Bolle
2015-05-21 23:52     ` Ray Jui
2015-05-22  8:39       ` Paul Bolle
2015-05-21 13:12   ` Kishon Vijay Abraham I
2015-05-21 21:35     ` Ray Jui
2015-05-21 21:51       ` Florian Fainelli
2015-05-21 22:02         ` Ray Jui [this message]
2015-05-20  1:23 ` [PATCH 3/5] phy: cygnus: pcie: Define DT binding Ray Jui
2015-05-21 13:14   ` Kishon Vijay Abraham I
2015-05-21 21:59     ` Ray Jui
2015-05-21 23:36       ` Ray Jui
2015-05-20  1:23 ` [PATCH 4/5] phy: cygnus: pcie: Add Cygnus PCIe PHY support Ray Jui
2015-05-21  7:52   ` Paul Bolle
2015-05-21 23:53     ` Ray Jui
2015-05-22  8:47       ` Paul Bolle
2015-05-21 13:19   ` Kishon Vijay Abraham I
2015-05-20  1:23 ` [PATCH 5/5] ARM: dts: enable PCIe PHY support for Cygnus Ray Jui

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=555E5602.7020801@broadcom.com \
    --to=rjui@broadcom.com \
    --cc=arunp@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=jdzheng@broadcom.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.