From: Andrew Lunn <andrew@lunn.ch>
To: Arun Parameswaran <arun.parameswaran@broadcom.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 0/3] Add Broadcom Omega SoC internal switch and phy
Date: Tue, 7 Aug 2018 20:08:27 +0200 [thread overview]
Message-ID: <20180807180827.GH18350@lunn.ch> (raw)
In-Reply-To: <1533661364-15381-1-git-send-email-arun.parameswaran@broadcom.com>
On Tue, Aug 07, 2018 at 10:02:41AM -0700, Arun Parameswaran wrote:
> Hi,
>
> The patchset is based on David Miller's "net-next" repo.
>
> The patches add support for the Broadcom Omega SoC's internal ethernet
> switch and the internal gphy.
>
> The internal ethernet switch in the Omega is a b53 srab based switch.
> The support for the switch is added to the b53 driver in the dsa
> framework.
>
> The gphy support is added to the bcm7xxx driver.
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2018-08-07 18:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:02 [PATCH 0/3] Add Broadcom Omega SoC internal switch and phy Arun Parameswaran
2018-08-07 17:02 ` [PATCH 1/3] dt-bindings: net: dsa: Add compatibility strings for Broadcom Omega Arun Parameswaran
2018-08-07 17:06 ` Florian Fainelli
2018-08-14 20:41 ` Rob Herring
2018-08-07 17:02 ` [PATCH 2/3] net: dsa: b53: Add support for Broadcom Omega SoC internal switch Arun Parameswaran
2018-08-07 17:06 ` Florian Fainelli
2018-08-07 17:02 ` [PATCH 3/3] net: phy: Add support for Broadcom Omega internal Combo GPHY Arun Parameswaran
2018-08-07 17:06 ` Florian Fainelli
2018-08-07 18:08 ` Andrew Lunn [this message]
2018-08-07 22:49 ` [PATCH 0/3] Add Broadcom Omega SoC internal switch and phy 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=20180807180827.GH18350@lunn.ch \
--to=andrew@lunn.ch \
--cc=arun.parameswaran@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@savoirfairelinux.com \
/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).