From: Simon Horman <horms@kernel•org>
To: Maxime Chevallier <maxime.chevallier@bootlin•com>
Cc: Andrew Lunn <andrew@lunn•ch>, Jakub Kicinski <kuba@kernel•org>,
davem@davemloft•net, Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
Woojung Huh <woojung.huh@microchip•com>,
Vladimir Oltean <olteanv@gmail•com>,
UNGLinuxDriver@microchip•com, thomas.petazzoni@bootlin•com,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH net-next] net: dsa: microchip: Don't embed struct phy_device to maintain the port state
Date: Fri, 20 Mar 2026 17:32:10 +0000 [thread overview]
Message-ID: <20260320173210.GF74886@horms.kernel.org> (raw)
In-Reply-To: <20260319181705.1576679-1-maxime.chevallier@bootlin.com>
On Thu, Mar 19, 2026 at 07:17:04PM +0100, Maxime Chevallier wrote:
> The KSZ9477 maintains the SGMII port's state for speed, duplex and link
> status to be able to fixup the accesses to its internal older version of
> the Designware XPCS. However, it does so by embedding a full instance of
> struct phy_device, only to use the 'speed', 'link' and 'duplex' fields.
>
> This is also only used for the SGMII port, it's otherwise unused for all
> other regular ports.
>
> Replace that with simple int/bool values.
>
> Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin•com>
Reviewed-by: Simon Horman <horms@kernel•org>
next prev parent reply other threads:[~2026-03-20 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:17 [PATCH net-next] net: dsa: microchip: Don't embed struct phy_device to maintain the port state Maxime Chevallier
2026-03-20 17:32 ` Simon Horman [this message]
2026-03-21 2:50 ` 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=20260320173210.GF74886@horms.kernel.org \
--to=horms@kernel$(echo .)org \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maxime.chevallier@bootlin$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olteanv@gmail$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=thomas.petazzoni@bootlin$(echo .)com \
--cc=woojung.huh@microchip$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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