From: Florian Fainelli <f.fainelli@gmail.com>
To: Michal Kubecek <mkubecek@suse.cz>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
Jiri Pirko <jiri@resnulli.us>, Andrew Lunn <andrew@lunn.ch>,
John Linville <linville@tuxdriver.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 4/5] ethtool: move string arrays into common file
Date: Wed, 11 Dec 2019 20:03:22 -0800 [thread overview]
Message-ID: <f6ff9fed-de34-7a4b-d929-99f06ecff8c4@gmail.com> (raw)
In-Reply-To: <19c54ebe20401b61df64e9bf3090c39b7126f5d7.1576057593.git.mkubecek@suse.cz>
On 12/11/2019 1:58 AM, Michal Kubecek wrote:
> Introduce file net/ethtool/common.c for code shared by ioctl and netlink
> ethtool interface. Move name tables of features, RSS hash functions,
> tunables and PHY tunables into this file.
>
> Signed-off-by: Michal Kubecek <mkubecek@suse.cz>
> Reviewed-by: Jiri Pirko <jiri@mellanox.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
--
Florian
next prev parent reply other threads:[~2019-12-12 4:03 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 [this message]
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
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=f6ff9fed-de34-7a4b-d929-99f06ecff8c4@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--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).