[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170412132450.GD1952@nanopsycho>
Date: Wed, 12 Apr 2017 15:24:50 +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 v5 4/5] netlink: pass extended ACK struct to
parsing functions
Wed, Apr 12, 2017 at 03:20:36PM CEST, johannes@...solutions.net wrote:
>On Wed, 2017-04-12 at 15:17 +0200, Jiri Pirko wrote:
>> Wed, Apr 12, 2017 at 02:34:07PM CEST, johannes@...solutions.net
>> wrote:
>> > From: Johannes Berg <johannes.berg@...el.com>
>> >
>> > Pass the new extended ACK reporting struct to all of the
>>
>> Johannes, I wonder, is there a reason you ignore my comments about
>> narrow descriptions? Why don't you use the whole line?
>
>I don't think it makes sense. Text is easier to read if it's narrower,
>80 columns was never desired (only 72), and frankly, I think discussing
>the commit or comment line length is pretty useless.
You are the only one not using 72 chars for some undefined reasons.
But in patch 3/5 you actually do. Sorry but that is just weird.
All I'm saying.
Powered by blists - more mailing lists