[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1a505546-5f08-fcae-6b0a-37add6a02669@gmail.com>
Date: Tue, 16 Jan 2018 20:06:30 -0800
From: David Ahern <dsahern@...il.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
Jiri Pirko <jiri@...nulli.us>
Cc: davem@...emloft.net, daniel@...earbox.net,
alexei.starovoitov@...il.com, netdev@...r.kernel.org,
oss-drivers@...ronome.com, john.fastabend@...il.com,
jhs@...atatu.com, gerlitz.or@...il.com, aring@...atatu.com,
xiyou.wangcong@...il.com,
Quentin Monnet <quentin.monnet@...ronome.com>
Subject: Re: [PATCH bpf-next v2 09/11] nfp: bpf: use extack support to improve
debugging
On 1/16/18 12:11 PM, Jakub Kicinski wrote:
> On Tue, 16 Jan 2018 10:36:01 +0100, Jiri Pirko wrote:
>>> @@ -303,7 +305,8 @@ static int nfp_net_bpf_load(struct nfp_net *nn, struct bpf_prog *prog)
>>> /* Load up the JITed code */
>>> err = nfp_net_reconfig(nn, NFP_NET_CFG_UPDATE_BPF);
>>> if (err)
>>> - nn_err(nn, "FW command error while loading BPF: %d\n", err);
>>> + NL_SET_ERR_MSG_MOD(extack,
>>> + "FW command error while loading BPF");
>>
>> One line please. Same for all others. Strings may overflow 80 cols.
>
> Sorry, but this is the way I want things in the nfp driver. If the
> string would fit 80 chars placed on a new line, it should be placed
> on a new line. If it doesn't fit anyway the new line is unnecessary.
> This rules is adhered to throughout the driver (to the extent I'm able
> to enforce it).
>
+1
Powered by blists - more mailing lists