public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Golle <daniel@makrotopia.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Vladimir Oltean <olteanv@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Frank Wunderlich <frankwu@gmx.de>,
	Chad Monroe <chad@monroe.io>,
	Cezary Wilmanski <cezary.wilmanski@adtran.com>,
	Liang Xu <lxu@maxlinear.com>, John Crispin <john@phrozen.org>
Subject: Re: [PATCH net-next v14 0/4] net: dsa: initial support for MaxLinear MxL862xx switches
Date: Wed, 11 Feb 2026 10:01:44 +0000	[thread overview]
Message-ID: <aYxTiJW03q1DN9XF@makrotopia.org> (raw)
In-Reply-To: <d6393a14-fe50-426d-9dd8-5a33b2af0a0d@redhat.com>

On Wed, Feb 11, 2026 at 10:49:56AM +0100, Paolo Abeni wrote:
> On 2/7/26 10:47 PM, Vladimir Oltean wrote:
> > On Sat, Feb 07, 2026 at 03:06:48AM +0000, Daniel Golle wrote:
> >> This series adds very basic DSA support for the MaxLinear MxL86252
> >> (5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
> >> In addition to the 2.5G TP ports both switches also come with two
> >> SerDes interfaces which can be used either to connect external PHYs
> >> or SFP cages, or as CPU port when using the switch with this DSA driver.
> > 
> > For the entire set:
> > 
> > Reviewed-by: Vladimir Oltean <olteanv@gmail.com>
> > 
> > with some minor comments I'll leave in individual patches, which I'd
> > like you to address.
> > 
> > I don't want to put anybody in a bad spot, but given what time it is,
> > this set should get at least _some_ time in net-next before the upcoming
> > net-next PR, to allow for some reaction time in case of some unexpected
> > reports like from static analysis or similar. 
> 
> As I'm wrapping-up the PR right now, and the series is not applied yet,
> I fear the above is not going to happen.
> 
> Since a driver is involved (as opposed to the core stack) and there will
> be the usual release cycle to address issues before the code lands in an
> official release, I tend to think this series should still be merged -
> unless someone voices strong and valid concerns _very soon_.
> 
> Thanks,
> 
> Paolo
> 
> So it would be good,
> > because of that, for the fixups as a result of my comments to be
> > separate patches rather than a new version.

Meaning I should send them *now*, despite net-next being closed already?

  parent reply	other threads:[~2026-02-11 10:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07  3:06 [PATCH net-next v14 0/4] net: dsa: initial support for MaxLinear MxL862xx switches Daniel Golle
2026-02-07  3:07 ` [PATCH net-next v14 1/4] dt-bindings: net: dsa: add MaxLinear MxL862xx Daniel Golle
2026-02-07 21:48   ` Vladimir Oltean
2026-02-07  3:07 ` [PATCH net-next v14 2/4] net: dsa: add tag format for MxL862xx switches Daniel Golle
2026-02-07  3:07 ` [PATCH net-next v14 3/4] net: mdio: add unlocked mdiodev C45 bus accessors Daniel Golle
2026-02-07  3:07 ` [PATCH net-next v14 4/4] net: dsa: add basic initial driver for MxL862xx switches Daniel Golle
2026-02-07 21:59   ` Vladimir Oltean
2026-02-08  0:06     ` Daniel Golle
2026-02-07 21:47 ` [PATCH net-next v14 0/4] net: dsa: initial support for MaxLinear " Vladimir Oltean
2026-02-11  9:49   ` Paolo Abeni
2026-02-11  9:57     ` Vladimir Oltean
2026-02-11 10:01     ` Daniel Golle [this message]
2026-02-11 10:09       ` Paolo Abeni
2026-02-11 11:10 ` 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=aYxTiJW03q1DN9XF@makrotopia.org \
    --to=daniel@makrotopia.org \
    --cc=andrew@lunn.ch \
    --cc=cezary.wilmanski@adtran.com \
    --cc=chad@monroe.io \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=frankwu@gmx.de \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=john@phrozen.org \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lxu@maxlinear.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=robh@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