From: Vladimir Oltean <olteanv@gmail.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
UNGLinuxDriver@microchip.com,
Woojung Huh <woojung.huh@microchip.com>
Subject: Re: [PATCH RFC net-next 0/7] net: dsa: cleanup EEE (part 2)
Date: Thu, 12 Dec 2024 21:48:53 +0200 [thread overview]
Message-ID: <20241212194853.7b2bic2vchuqprxz@skbuf> (raw)
In-Reply-To: <Z1hPaLFlR4TW_YCr@shell.armlinux.org.uk>
On Tue, Dec 10, 2024 at 02:25:44PM +0000, Russell King (Oracle) wrote:
> This is part 2 of the DSA EEE cleanups, and is being sent out becaues it
> is relevant for the review of part 1, but would make part 1 too large.
>
> Patch 1 removes the useless setting of tx_lpi parameters in the
> ksz driver.
>
> Patch 2 removes the DSA core code that calls the get_mac_eee() operation.
> This needs to be done before removing the implementations because doing
> otherwise would cause dsa_user_get_eee() to return -EOPNOTSUPP.
>
> Patches 3..6 remove the trivial get_mac_eee() implementations from DSA
> drivers.
>
> Patch 7 finally removes the get_mac_eee() method from struct
> dsa_switch_ops.
I appreciate the splitting of the get_mac_eee() removal into multiple
patches per driver and 2 for the DSA framework. It should help BSP
backporters which target only a subset of DSA drivers. Monolithic
patches are harder to digest, and may have trivial context conflicts due
to unrelated changes.
The set looks good, please don't forget to also update the documentation.
next prev parent reply other threads:[~2024-12-12 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 14:25 [PATCH RFC net-next 0/7] net: dsa: cleanup EEE (part 2) Russell King (Oracle)
2024-12-10 14:26 ` [PATCH RFC net-next 1/7] net: dsa: ksz: remove setting of tx_lpi parameters Russell King (Oracle)
2024-12-12 19:38 ` Vladimir Oltean
2024-12-10 14:26 ` [PATCH RFC net-next 2/7] net: dsa: no longer call ds->ops->get_mac_eee() Russell King (Oracle)
2024-12-12 19:44 ` Vladimir Oltean
2025-01-02 17:56 ` Russell King (Oracle)
2024-12-10 14:26 ` [PATCH RFC net-next 3/7] net: dsa: b53/bcm_sf2: remove b53_get_mac_eee() Russell King (Oracle)
2024-12-10 14:26 ` [PATCH RFC net-next 4/7] net: dsa: ksz: remove ksz_get_mac_eee() Russell King (Oracle)
2024-12-10 14:26 ` [PATCH RFC net-next 5/7] net: dsa: mv88e6xxx: remove mv88e6xxx_get_mac_eee() Russell King (Oracle)
2024-12-10 14:26 ` [PATCH RFC net-next 6/7] net: dsa: qca: remove qca8k_get_mac_eee() Russell King (Oracle)
2024-12-10 14:26 ` [PATCH RFC net-next 7/7] net: dsa: remove get_mac_eee() method Russell King (Oracle)
2024-12-12 19:48 ` Vladimir Oltean [this message]
2025-01-02 18:18 ` [PATCH RFC net-next 0/7] net: dsa: cleanup EEE (part 2) Russell King (Oracle)
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=20241212194853.7b2bic2vchuqprxz@skbuf \
--to=olteanv@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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