[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191210095134.27f46a81@cakuba.netronome.com>
Date: Tue, 10 Dec 2019 09:51:34 -0800
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Michal Kubecek <mkubecek@...e.cz>
Cc: David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
Jiri Pirko <jiri@...nulli.us>, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
John Linville <linville@...driver.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Johannes Berg <johannes@...solutions.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/5] ethtool netlink interface, preliminary
part
On Tue, 10 Dec 2019 14:07:48 +0100 (CET), Michal Kubecek wrote:
> As Jakub Kicinski suggested in ethtool netlink v7 discussion, this
> submission consists only of preliminary patches which raised no objections;
> first four patches already have Acked-by or Reviewed-by.
>
> - patch 1 exposes permanent hardware address (as shown by "ethtool -P")
> via rtnetlink
> - patch 2 is renames existing netlink helper to a better name
> - patch 3 and 4 reorganize existing ethtool code (no functional change)
> - patch 5 makes the table of link mode names available as an ethtool string
> set (will be needed for the netlink interface)
>
> Once we get these out of the way, v8 of the first part of the ethtool
> netlink interface will follow.
Reviewed-by: Jakub Kicinski <jakub.kicinski@...ronome.com>
Thank you!
Powered by blists - more mailing lists