From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 0/2] net: dsa: bcm_sf2: Utilize PHYLINK for all ports
Date: Wed, 17 Aug 2022 10:56:00 -0700 [thread overview]
Message-ID: <20220817105600.2aa3612c@kernel.org> (raw)
In-Reply-To: <20220817172704.ne3cwqcfzplt2pgp@skbuf>
On Wed, 17 Aug 2022 20:27:04 +0300 Vladimir Oltean wrote:
> On Wed, Aug 17, 2022 at 08:54:14AM -0700, Jakub Kicinski wrote:
> > On Mon, 15 Aug 2022 10:50:07 -0700 Florian Fainelli wrote:
> > > Hi all,
> > >
> > > This patch series has the bcm_sf2 driver utilize PHYLINK to configure
> > > the CPU port link parameters to unify the configuration and pave the way
> > > for DSA to utilize PHYLINK for all ports in the future.
> > >
> > > Tested on BCM7445 and BCM7278
> >
> > Last call for reviews..
>
> My review is: let's see what breaks...
*nod*, thanks!
next prev parent reply other threads:[~2022-08-17 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 17:50 [PATCH net-next 0/2] net: dsa: bcm_sf2: Utilize PHYLINK for all ports Florian Fainelli
2022-08-15 17:50 ` [PATCH net-next 1/2] net: dsa: bcm_sf2: Introduce helper for port override offset Florian Fainelli
2022-08-15 17:50 ` [PATCH net-next 2/2] net: dsa: bcm_sf2: Have PHYLINK configure CPU/IMP port(s) Florian Fainelli
2022-08-17 15:54 ` [PATCH net-next 0/2] net: dsa: bcm_sf2: Utilize PHYLINK for all ports Jakub Kicinski
2022-08-17 17:27 ` Vladimir Oltean
2022-08-17 17:56 ` Jakub Kicinski [this message]
2022-08-17 18:40 ` patchwork-bot+netdevbpf
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=20220817105600.2aa3612c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.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).