[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aac5ee76680d9ea445f09894e161fa1fb66884a8.camel@perches.com>
Date: Wed, 21 Sep 2022 09:56:07 -0700
From: Joe Perches <joe@...ches.com>
To: Niklas Söderlund
<niklas.soderlund@...igine.com>
Cc: Dwaipayan Ray <dwaipayanray1@...il.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Jonathan Corbet <corbet@....net>,
Andy Whitcroft <apw@...onical.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
Philippe Schenker <philippe.schenker@...adex.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
oss-drivers@...igine.com, Simon Horman <simon.horman@...igine.com>,
Louis Peens <louis.peens@...igine.com>
Subject: Re: [PATCH v7] checkpatch: warn for non-standard fixes tag style
On Wed, 2022-09-21 at 16:25 +0200, Niklas Söderlund wrote:
> Hello Joe,
Hello Niklas
> Just wanted to check on my misunderstanding below before posting a v8.
I think v7 is ok, unless you found something else better.
> > > One grep pattern to verify the non canonical fixes format that
> > > are mistakenly used is:
> > >
> > > $ git log --since=5-years-ago --no-merges --grep='^\s*fixes' -i --format=email -P | \
> > > grep -P -i '^\s*fixes' | \
> > > grep -P -v '^Fixes: [0-9a-f]{12,12}\s*\(".*")'
> > > There are many different styles.
> > > Parentheses are sometimes not used.
> >
> > I understand this, and I did have a look at it.
Good enough for me. Thanks.
Powered by blists - more mailing lists