[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201119212122.665d5396@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Thu, 19 Nov 2020 21:21:22 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Heiner Kallweit <hkallweit1@...il.com>
Cc: Andrew Lunn <andrew@...n.ch>,
Grygorii Strashko <grygorii.strashko@...com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] mdio_bus: suppress err message for reset gpio
EPROBE_DEFER
On Thu, 19 Nov 2020 23:09:52 +0100 Heiner Kallweit wrote:
> Am 19.11.2020 um 22:41 schrieb Andrew Lunn:
> >>>> Doesn't checkpatch complain about line length > 80 here?
> >>>
> >>> :)
> >>>
> >>> commit bdc48fa11e46f867ea4d75fa59ee87a7f48be144
> >>> Author: Joe Perches <joe@...ches.com>
> >>> Date: Fri May 29 16:12:21 2020 -0700
> >>>
> >>> checkpatch/coding-style: deprecate 80-column warning
> >>>
> >>
> >> Ah, again something learnt. Thanks for the reference.
> >
> > But it then got revoked for netdev. Or at least it was planned to
> > re-impose 80 for netdev. I don't know if checkpatch got patched yet.
FWIW I had a patch for it but before I sent it Dave suggested I ask
around and Alexei was opposed.
And I don't have the strength to argue :)
I'll just tell people case by case when they have 4+ indentation levels
in their code or use 40+ character variables/defines, in my copious
spare time.
> At a first glance it sounds strange that subsystems may define own
> rules for such basic things. But supposedly there has been a longer
> emotional disucssion about this already ..
We do have our own comment style rule in networking since the beginning
of time, and reverse xmas tree, so it's not completely crazy.
Powered by blists - more mailing lists