linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	pablo@netfilter.org, Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Benc <jbenc@redhat.com>,
	David Ahern <dsa@cumulusnetworks.com>,
	Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH net-next v5 5/5] netlink: pass extended ACK struct where available
Date: Wed, 12 Apr 2017 16:00:43 +0200	[thread overview]
Message-ID: <20170412140043.GH1952@nanopsycho> (raw)
In-Reply-To: <20170412123408.22012-6-johannes@sipsolutions.net>

Wed, Apr 12, 2017 at 02:34:08PM CEST, johannes@sipsolutions.net wrote:
>From: Johannes Berg <johannes.berg@intel.com>
>
>This is an add-on to the previous patch that passes
>the extended ACK structure where it's already available
>by existing genl_info or extack function arguments.
>
>This was done with this spatch (with some manual
>adjustment of indentation):
>
>@@
>expression A, B, C, D, E;
>identifier fn, info;
>@@
>fn(..., struct genl_info *info, ...) {
>...
>-nlmsg_parse(A, B, C, D, E, NULL)
>+nlmsg_parse(A, B, C, D, E, info->extack)
>...
>}
>
>@@
>expression A, B, C, D, E;
>identifier fn, info;
>@@
>fn(..., struct genl_info *info, ...) {
><...
>-nla_parse_nested(A, B, C, D, NULL)
>+nla_parse_nested(A, B, C, D, info->extack)
>...>
>}
>
>@@
>expression A, B, C, D, E;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
><...
>-nlmsg_parse(A, B, C, D, E, NULL)
>+nlmsg_parse(A, B, C, D, E, extack)
>...>
>}
>
>@@
>expression A, B, C, D, E;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
><...
>-nla_parse(A, B, C, D, E, NULL)
>+nla_parse(A, B, C, D, E, extack)
>...>
>}
>
>@@
>expression A, B, C, D, E;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
>...
>-nlmsg_parse(A, B, C, D, E, NULL)
>+nlmsg_parse(A, B, C, D, E, extack)
>...
>}
>
>@@
>expression A, B, C, D;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
><...
>-nla_parse_nested(A, B, C, D, NULL)
>+nla_parse_nested(A, B, C, D, extack)
>...>
>}
>
>@@
>expression A, B, C, D;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
><...
>-nlmsg_validate(A, B, C, D, NULL)
>+nlmsg_validate(A, B, C, D, extack)
>...>
>}
>
>@@
>expression A, B, C, D;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
><...
>-nla_validate(A, B, C, D, NULL)
>+nla_validate(A, B, C, D, extack)
>...>
>}
>
>@@
>expression A, B, C;
>identifier fn, extack;
>@@
>fn(..., struct netlink_ext_ack *extack, ...) {
><...
>-nla_validate_nested(A, B, C, NULL)
>+nla_validate_nested(A, B, C, extack)
>...>
>}
>
>Signed-off-by: Johannes Berg <johannes.berg@intel.com>
>---
> crypto/crypto_user.c           |  2 +-
> drivers/net/team/team.c        |  3 ++-
> net/ieee802154/nl802154.c      | 10 +++++-----
> net/netfilter/ipvs/ip_vs_ctl.c |  2 +-
> net/netfilter/nfnetlink.c      |  2 +-
> net/netlink/genetlink.c        |  2 +-
> net/nfc/netlink.c              |  2 +-
> net/tipc/bearer.c              | 14 +++++++-------
> net/tipc/net.c                 |  2 +-
> net/tipc/node.c                |  8 ++++----
> net/wireless/nl80211.c         | 33 ++++++++++++++++++---------------
> net/xfrm/xfrm_user.c           |  2 +-
> 12 files changed, 43 insertions(+), 39 deletions(-)

Aside from the tinyfication of desc lines, this looks good to me

Reviewed-by: Jiri Pirko <jiri@mellanox.com>

  reply	other threads:[~2017-04-12 14:00 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 12:34 [PATCH net-next v5 0/5] netlink extended ACK reporting Johannes Berg
2017-04-12 12:34 ` [PATCH net-next v5 1/5] netlink: " Johannes Berg
2017-04-12 13:41   ` Jiri Pirko
2017-04-12 15:06   ` David Ahern
2017-04-12 15:13     ` Jiri Pirko
2017-04-12 15:28       ` David Miller
2017-04-12 15:21     ` Johannes Berg
2017-04-12 15:30       ` David Miller
2017-04-12 15:32   ` David Ahern
2017-04-12 12:34 ` [PATCH net-next v5 2/5] genetlink: pass extended ACK report down Johannes Berg
2017-04-12 14:01   ` Jiri Pirko
2017-04-12 12:34 ` [PATCH net-next v5 3/5] netlink: allow sending extended ACK with cookie on success Johannes Berg
2017-04-12 13:47   ` Jiri Pirko
2017-04-12 13:54     ` Johannes Berg
2017-04-12 12:34 ` [PATCH net-next v5 4/5] netlink: pass extended ACK struct to parsing functions Johannes Berg
2017-04-12 13:17   ` Jiri Pirko
2017-04-12 13:20     ` Johannes Berg
2017-04-12 13:24       ` Jiri Pirko
2017-04-12 14:02     ` Kalle Valo
2017-04-12 14:08       ` Jiri Pirko
2017-04-12 13:56   ` Jiri Pirko
2017-04-12 12:34 ` [PATCH net-next v5 5/5] netlink: pass extended ACK struct where available Johannes Berg
2017-04-12 14:00   ` Jiri Pirko [this message]
2017-04-12 14:55     ` David Ahern
2017-04-12 15:15       ` Jiri Pirko
2017-04-12 15:29         ` David Miller
2017-04-12 14:57 ` [PATCH net-next v5 0/5] netlink extended ACK reporting David Ahern

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=20170412140043.GH1952@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=dsa@cumulusnetworks.com \
    --cc=jbenc@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.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).