[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170411081346.GD1976@nanopsycho>
Date: Tue, 11 Apr 2017 10:13:46 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Johannes Berg <johannes@...solutions.net>
Cc: linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
pablo@...filter.org, Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Benc <jbenc@...hat.com>,
David Ahern <dsa@...ulusnetworks.com>
Subject: Re: [PATCH net-next v4 1/5] netlink: extended ACK reporting
Tue, Apr 11, 2017 at 09:29:18AM CEST, johannes@...solutions.net wrote:
>On Tue, 2017-04-11 at 09:19 +0200, Jiri Pirko wrote:
>>
>> > + NUM_NLMSGERR_ATTRS,
>>
>> According to the rest of the uapi, this should be rather named:
>> __NLMSGERR_ATTR_MAX
>
>nl80211 uses NUM_ so I guess that's a matter of convention, but I can
>change that I guess.
Please do.
>
>> > if (err || (nlh->nlmsg_flags & NLM_F_ACK))
>> > - netlink_ack(skb, nlh, err);
>> > + netlink_ack(skb, nlh, err, NULL);
>>
>> Wouldn't it make sense to leave netlink_ack as is and add
>> netlink_ack_ext for those who need to pass non-null?
>
>I thought about it, but didn't really see much point. The churn isn't
>super big (a dozen callers or so), and I thought it makes sense to
>point out to the users that there's something here.
Makes sense.
Powered by blists - more mailing lists