linux-kernel - Re: [PATCH 5/6] staging: lustre: lustre: several over 80 characters cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170623161258.GA20104@kroah.com>
Date:   Sat, 24 Jun 2017 00:12:58 +0800
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     James Simmons <jsimmons@...radead.org>
Cc:     Joe Perches <joe@...ches.com>, devel@...verdev.osuosl.org,
        Andreas Dilger <andreas.dilger@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Oleg Drokin <oleg.drokin@...el.com>,
        Lustre Development List <lustre-devel@...ts.lustre.org>
Subject: Re: [PATCH 5/6] staging: lustre: lustre: several over 80 characters
 cleanups

On Thu, Jun 15, 2017 at 05:06:30PM +0100, James Simmons wrote:
> 
> > On Wed, 2017-06-14 at 11:01 -0400, James Simmons wrote:
> > > Cleanup many of the over 80 characters reported by checkpatch
> > 
> > Please don't let checkpatch get in the way of lustre
> > readability.
> > 
> > lustre commonly uses very long identifiers.
> > Long identifiers and 80 columns don't mix well.
> > 
> > It might be simpler to declare in some document that
> > lustre uses lines of up to whatever length and require
> > that checkpatch should be used with the --max-line-length
> > option when run on lustre code.
> 
> Greg would you be okay with this? If we changed to a max-line-length to 
> say 128 thay would mean very few checkpatch issues would remain.

No, I don't want you go change the max-line-length, just use your best
judgement.  Some of the changes here in this very-big patch are just
fine, and should be done as they make the code easier to read.

Others, you are just having to fix pedantic things and there's no need
for that.  Let me give you a few examples in this patch of what I'm
talking about to help you understand the difference...

thanks,

greg k-h