From: Paolo Abeni <pabeni@redhat.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Woojung Huh <woojung.huh@microchip.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King <rmk+kernel@armlinux.org.uk>,
Thangaraj Samynathan <Thangaraj.S@microchip.com>,
Rengarajan Sundararajan <Rengarajan.S@microchip.com>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
Phil Elwell <phil@raspberrypi.org>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next v7 08/12] net: usb: lan78xx: Convert to PHYLINK for improved PHY and MAC management
Date: Fri, 2 May 2025 11:39:28 +0200 [thread overview]
Message-ID: <cb94f33f-2e74-4e5d-8f68-58322a290ffb@redhat.com> (raw)
In-Reply-To: <20250428130542.3879769-9-o.rempel@pengutronix.de>
On 4/28/25 3:05 PM, Oleksij Rempel wrote:
> @@ -384,7 +385,7 @@ struct skb_data { /* skb->cb is one of these */
> #define EVENT_RX_HALT 1
> #define EVENT_RX_MEMORY 2
> #define EVENT_STS_SPLIT 3
> -#define EVENT_LINK_RESET 4
> +#define EVENT_PHY_INT_ACK 4
The patch is quite large as-is. The bit rename should possibly go in a
separate patch.
/P
next prev parent reply other threads:[~2025-05-02 9:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 13:05 [PATCH net-next v7 00/12] Convert LAN78xx to PHYLINK Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 01/12] net: usb: lan78xx: Improve error handling in PHY initialization Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 02/12] net: usb: lan78xx: remove explicit check for missing PHY driver Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 03/12] net: usb: lan78xx: refactor PHY init to separate detection and MAC configuration Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 04/12] net: usb: lan78xx: move LED DT configuration to helper Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 05/12] net: usb: lan78xx: Extract PHY interrupt acknowledgment " Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 06/12] net: usb: lan78xx: Refactor USB link power configuration into helper Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 07/12] net: usb: lan78xx: Extract flow control configuration to helper Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 08/12] net: usb: lan78xx: Convert to PHYLINK for improved PHY and MAC management Oleksij Rempel
2025-05-02 9:36 ` Paolo Abeni
2025-05-02 9:39 ` Paolo Abeni [this message]
2025-04-28 13:05 ` [PATCH net-next v7 09/12] net: usb: lan78xx: Use ethtool_op_get_link to reflect current link status Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 10/12] net: usb: lan78xx: port link settings to phylink API Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 11/12] net: usb: lan78xx: Integrate EEE support with phylink LPI API Oleksij Rempel
2025-04-28 13:05 ` [PATCH net-next v7 12/12] net: usb: lan78xx: remove unused struct members Oleksij Rempel
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=cb94f33f-2e74-4e5d-8f68-58322a290ffb@redhat.com \
--to=pabeni@redhat.com \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=phil@raspberrypi.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=woojung.huh@microchip.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