From: Arun Parameswaran <arun.parameswaran@broadcom.com>
To: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
open list <linux-kernel@vger.kernel.org>,
hkallweit1@gmail.com, bcm-kernel-feedback-list@broadcom.com,
murali.policharla@broadcom.com
Subject: Re: [PATCH net-next 0/2] net: phy: Move Omega PHY entry to Cygnus PHY driver
Date: Wed, 20 Mar 2019 13:51:39 -0700 [thread overview]
Message-ID: <b4882cd3-c6c7-6af8-2204-6627434b03cf@broadcom.com> (raw)
In-Reply-To: <20190320195313.15658-1-f.fainelli@gmail.com>
Thanks Florian.
For the patch series,
Acked-by: Arun Parameswaran <arun.parameswaran@broadcom.com>
On 2019-03-20 12:53 p.m., Florian Fainelli wrote:
> Hi,
>
> In order to pave the way for adding some specific Omega PHY features
> that may not be desirable on other products covered by the bcm7xxx PHY
> driver, split the Omega PHY entry into the Cygnus PHY driver such that
> the PHY drivers are reflective of product lines/business units
> maintaining them within Broadcom.
>
> No functional changes intended.
>
> Florian Fainelli (2):
> net: phy: Prepare for moving Omega out of bcm7xxx
> net: phy: Move Omega PHY entry to Cygnus PHY driver
>
> drivers/net/phy/Kconfig | 5 +-
> drivers/net/phy/bcm-cygnus.c | 147 +++++++++++++++++++++++++++++++++-
> drivers/net/phy/bcm-phy-lib.c | 52 ++++++++++++
> drivers/net/phy/bcm-phy-lib.h | 20 +++++
> drivers/net/phy/bcm7xxx.c | 76 +-----------------
> 5 files changed, 225 insertions(+), 75 deletions(-)
>
next prev parent reply other threads:[~2019-03-20 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 19:53 [PATCH net-next 0/2] net: phy: Move Omega PHY entry to Cygnus PHY driver Florian Fainelli
2019-03-20 19:53 ` [PATCH net-next 1/2] net: phy: Prepare for moving Omega out of bcm7xxx Florian Fainelli
2019-03-20 22:34 ` Scott Branden
2019-03-20 19:53 ` [PATCH net-next 2/2] net: phy: Move Omega PHY entry to Cygnus PHY driver Florian Fainelli
2019-03-20 22:35 ` Scott Branden
2019-03-20 20:51 ` Arun Parameswaran [this message]
2019-03-21 20:41 ` [PATCH net-next 0/2] " David Miller
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=b4882cd3-c6c7-6af8-2204-6627434b03cf@broadcom.com \
--to=arun.parameswaran@broadcom.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=murali.policharla@broadcom.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).