[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1423159299.4752.7.camel@perches.com>
Date: Thu, 05 Feb 2015 10:01:39 -0800
From: Joe Perches <joe@...ches.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Al Viro <viro@...IV.linux.org.uk>, devel@...verdev.osuosl.org,
Andreas Dilger <andreas.dilger@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, Oleg Drokin <oleg.drokin@...el.com>,
"Lad, Prabhakar" <prabhakar.csengg@...il.com>,
HPDD-discuss@...1.01.org, Andreas Ruprecht <rupran@...server.de>
Subject: Re: use of opaque subject lines
On Thu, 2015-02-05 at 20:35 +0300, Dan Carpenter wrote:
> On Thu, Feb 05, 2015 at 09:32:55AM -0800, Joe Perches wrote:
> > On Thu, 2015-02-05 at 09:31 -0800, Joe Perches wrote:
> > > On Thu, 2015-02-05 at 20:25 +0300, Dan Carpenter wrote:
> > > > Acked-by: Dan Carpenter <dan.carpenter@...cle.com>
> > > Maybe I should add sparse too... ;)
> > drat, of course I meant smatch...
> No need. Smatch users are awesome at writing changelogs.
:) good point, kinda...
$ git log --format=oneline | grep -wi smatch | wc -l
141
$ git log --pretty=oneline | grep -wi sparse | wc -l
2383
$ git log --pretty=oneline | grep -Pi "\bcheckpatch\b[^:]" | wc -l
1637
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists