netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v9 02/14] ethtool: helper functions for netlink interface
Date: Fri, 27 Dec 2019 08:32:30 -0800	[thread overview]
Message-ID: <56c2e350-09df-98cc-2a82-6360b1e98677@gmail.com> (raw)
In-Reply-To: <cbc22b1063fc4b1779ed33925bc339f4d767e702.1577457846.git.mkubecek@suse.cz>



On 12/27/2019 6:55 AM, Michal Kubecek wrote:
> Add common request/reply header definition and helpers to parse request
> header and fill reply header. Provide ethnl_update_* helpers to update
> structure members from request attributes (to be used for *_SET requests).
> 
> Signed-off-by: Michal Kubecek <mkubecek@suse.cz>

Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
-- 
Florian

  reply	other threads:[~2019-12-27 16:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 14:55 [PATCH net-next v9 00/14] ethtool netlink interface, part 1 Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 01/14] ethtool: introduce ethtool netlink interface Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 02/14] ethtool: helper functions for " Michal Kubecek
2019-12-27 16:32   ` Florian Fainelli [this message]
2019-12-27 14:55 ` [PATCH net-next v9 03/14] ethtool: netlink bitset handling Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 04/14] ethtool: support for netlink notifications Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 05/14] ethtool: default handlers for GET requests Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 06/14] ethtool: provide string sets with STRSET_GET request Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 07/14] ethtool: provide link settings with LINKINFO_GET request Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 08/14] ethtool: set link settings with LINKINFO_SET request Michal Kubecek
2019-12-27 14:55 ` [PATCH net-next v9 09/14] ethtool: add default notification handler Michal Kubecek
2019-12-27 14:56 ` [PATCH net-next v9 10/14] ethtool: add LINKINFO_NTF notification Michal Kubecek
2019-12-27 14:56 ` [PATCH net-next v9 11/14] ethtool: provide link mode information with LINKMODES_GET request Michal Kubecek
2019-12-27 14:56 ` [PATCH net-next v9 12/14] ethtool: set link modes related data with LINKMODES_SET request Michal Kubecek
2019-12-27 14:56 ` [PATCH net-next v9 13/14] ethtool: add LINKMODES_NTF notification Michal Kubecek
2019-12-27 14:56 ` [PATCH net-next v9 14/14] ethtool: provide link state with LINKSTATE_GET request Michal Kubecek
2019-12-28  0:42 ` [PATCH net-next v9 00/14] ethtool netlink interface, part 1 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=56c2e350-09df-98cc-2a82-6360b1e98677@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).