netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
	Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v4 0/6] ethtool: switch EEE netlink interface to use EEE linkmode bitmaps
Date: Mon, 29 Jan 2024 11:13:43 +0100	[thread overview]
Message-ID: <87a8bd8e-d1a5-4b1a-b70a-555e9fc15799@gmail.com> (raw)
In-Reply-To: <0a352643-8cc5-47b7-b31c-dc36ec69fa19@lunn.ch>

On 29.01.2024 01:10, Andrew Lunn wrote:
> On Sat, Jan 27, 2024 at 02:24:05PM +0100, Heiner Kallweit wrote:
>> So far only 32bit legacy bitmaps are passed to userspace. This makes
>> it impossible to manage EEE linkmodes beyond bit 32, e.g. manage EEE
>> for 2500BaseT and 5000BaseT. This series adds support for passing
>> full linkmode bitmaps between kernel and userspace.
>>
>> Fortunately the netlink-based part of ethtool is quite smart and no
>> changes are needed in ethtool. However this applies to the netlink
>> interface only, the ioctl interface for now remains restricted to
>> legacy bitmaps.
>>
>> Next step will be adding support for the c45 EEE2 standard registers
>> (3.21, 7.62, 7.63) to the genphy_c45 functions dealing with EEE.
>> I have a follow-up series for this ready to be submitted.
> 
> I tend to disagree. The next step should be to work on each driver
> still using supported_32 etc and convert them to use plain supported.
> 
> What i don't want is this conversion left half done. I said i'm happy
> to help convert the remaining drivers, so lets work on that.
> 
Fine with me, EEE2 can wait until this is done.

> My happy to merge this patchset, its a good intermediary step which
> allows each driver to be converted on its own. But i'm likely to NACK
> EEE2 until the _32 are gone.
> 
>      Andrew
Heiner


  reply	other threads:[~2024-01-29 10:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 13:24 [PATCH net-next v4 0/6] ethtool: switch EEE netlink interface to use EEE linkmode bitmaps Heiner Kallweit
2024-01-27 13:25 ` [PATCH net-next v4 1/6] ethtool: replace struct ethtool_eee with a new struct ethtool_keee on kernel side Heiner Kallweit
2024-01-28 23:54   ` Andrew Lunn
2024-01-27 13:26 ` [PATCH net-next v4 2/6] ethtool: switch back from ethtool_keee to ethtool_eee for ioctl Heiner Kallweit
2024-01-28 23:57   ` Andrew Lunn
2024-01-27 13:26 ` [PATCH net-next v4 3/6] ethtool: adjust struct ethtool_keee to kernel needs Heiner Kallweit
2024-01-27 13:28 ` [PATCH net-next v4 4/6] ethtool: add suffix _u32 to legacy bitmap members of struct ethtool_keee Heiner Kallweit
2024-01-29  0:13   ` Andrew Lunn
2024-01-27 13:29 ` [PATCH net-next v4 5/6] ethtool: add linkmode bitmap support to " Heiner Kallweit
2024-01-29  0:12   ` Andrew Lunn
2024-01-27 13:30 ` [PATCH net-next v4 6/6] net: phy: c45: change genphy_c45_ethtool_[get|set]_eee to use EEE linkmode bitmaps Heiner Kallweit
2024-01-29  0:10   ` Andrew Lunn
2024-01-29  0:10 ` [PATCH net-next v4 0/6] ethtool: switch EEE netlink interface " Andrew Lunn
2024-01-29 10:13   ` Heiner Kallweit [this message]
2024-01-31 12: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=87a8bd8e-d1a5-4b1a-b70a-555e9fc15799@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).