From: David Miller <davem@davemloft.net>
To: mkubecek@suse.cz
Cc: netdev@vger.kernel.org, jakub.kicinski@netronome.com,
jiri@resnulli.us, andrew@lunn.ch, f.fainelli@gmail.com,
linville@tuxdriver.com, stephen@networkplumber.org,
johannes@sipsolutions.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] ethtool netlink interface, preliminary part
Date: Thu, 12 Dec 2019 17:07:48 -0800 (PST) [thread overview]
Message-ID: <20191212.170748.409220660557209092.davem@davemloft.net> (raw)
In-Reply-To: <cover.1576057593.git.mkubecek@suse.cz>
From: Michal Kubecek <mkubecek@suse.cz>
Date: Wed, 11 Dec 2019 10:58:09 +0100 (CET)
> 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.
>
> Changes from v2 to v3: fix SPDX licence identifiers (patch 3 and 5).
>
> Changes from v1 to v2: restore build time check that all link modes have
> assigned a name (patch 5).
Series applied to net-next, thanks.
prev parent reply other threads:[~2019-12-13 1:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 9:58 [PATCH net-next v3 0/5] ethtool netlink interface, preliminary part Michal Kubecek
2019-12-11 9:58 ` [PATCH net-next v3 1/5] rtnetlink: provide permanent hardware address in RTM_NEWLINK Michal Kubecek
2019-12-11 9:58 ` [PATCH net-next v3 2/5] netlink: rename nl80211_validate_nested() to nla_validate_nested() Michal Kubecek
2019-12-11 9:58 ` [PATCH net-next v3 3/5] ethtool: move to its own directory Michal Kubecek
2019-12-11 9:58 ` [PATCH net-next v3 4/5] ethtool: move string arrays into common file Michal Kubecek
2019-12-12 4:03 ` Florian Fainelli
2019-12-11 9:58 ` [PATCH net-next v3 5/5] ethtool: provide link mode names as a string set Michal Kubecek
2019-12-12 4:12 ` Florian Fainelli
2019-12-11 17:46 ` [PATCH net-next v3 0/5] ethtool netlink interface, preliminary part Jakub Kicinski
2019-12-12 4:13 ` Florian Fainelli
2019-12-13 1:07 ` David Miller [this message]
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=20191212.170748.409220660557209092.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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).