[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1513030348.3036.5.camel@perches.com>
Date: Mon, 11 Dec 2017 14:12:28 -0800
From: Joe Perches <joe@...ches.com>
To: Dave Chinner <david@...morbit.com>
Cc: Alan Stern <stern@...land.harvard.edu>,
Byungchul Park <byungchul.park@....com>,
Theodore Ts'o <tytso@....edu>,
Matthew Wilcox <willy@...radead.org>,
Matthew Wilcox <mawilcox@...rosoft.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Jens Axboe <axboe@...nel.dk>,
Rehas Sachdeva <aquannie@...il.com>, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-nilfs@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-team@....com
Subject: Re: [PATCH v4 72/73] xfs: Convert mru cache to XArray
On Tue, 2017-12-12 at 08:43 +1100, Dave Chinner wrote:
> On Sat, Dec 09, 2017 at 09:00:18AM -0800, Joe Perches wrote:
> > On Sat, 2017-12-09 at 09:36 +1100, Dave Chinner wrote:
> > > 1. Using lockdep_set_novalidate_class() for anything other
> > > than device->mutex will throw checkpatch warnings. Nice. (*)
> > []
> > > (*) checkpatch.pl is considered mostly harmful round here, too,
> > > but that's another rant....
> >
> > How so?
>
> Short story is that it barfs all over the slightly non-standard
> coding style used in XFS.
[]
> This sort of stuff is just lowest-common-denominator noise - great
> for new code and/or inexperienced developers, but not for working
> with large bodies of existing code with slightly non-standard
> conventions.
Completely reasonable. Thanks.
Do you get many checkpatch submitters for fs/xfs?
If so, could probably do something about adding
a checkpatch file flag to the directory or equivalent.
Maybe add something like:
fs/xfs/.checkpatch
where the contents turn off most everything
Powered by blists - more mailing lists