From: Joe Perches <joe@perches.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
devel@driverdev.osuosl.org,
Andreas Dilger <andreas.dilger@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Oleg Drokin <oleg.drokin@intel.com>,
"Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
HPDD-discuss@ml01.01.org, Andreas Ruprecht <rupran@einserver.de>
Subject: Re: use of opaque subject lines
Date: Thu, 05 Feb 2015 10:01:39 -0800 [thread overview]
Message-ID: <1423159299.4752.7.camel@perches.com> (raw)
In-Reply-To: <20150205173552.GM5285@mwanda>
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@oracle.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
next prev parent reply other threads:[~2015-02-05 18:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:36 [PATCH] staging: lustre: osc: Fix sparse warning about osc_init Andreas Ruprecht
2015-02-02 14:16 ` Al Viro
2015-02-02 19:13 ` Andreas Ruprecht
2015-02-05 16:30 ` use of opaque subject lines Al Viro
2015-02-05 16:57 ` Lad, Prabhakar
2015-02-05 17:57 ` Greg Kroah-Hartman
2015-02-05 18:22 ` Lad, Prabhakar
2015-02-05 19:32 ` Paul Bolle
2015-02-05 20:06 ` Greg Kroah-Hartman
2015-02-05 20:53 ` Joe Perches
2015-02-05 17:08 ` Joe Perches
2015-02-05 17:25 ` Dan Carpenter
2015-02-05 17:31 ` Joe Perches
2015-02-05 17:32 ` Joe Perches
2015-02-05 17:35 ` Dan Carpenter
2015-02-05 18:01 ` Joe Perches [this message]
2015-02-05 18:26 ` Dan Carpenter
2015-02-05 18:03 ` Greg Kroah-Hartman
2015-02-02 19:24 ` [PATCH] staging: lustre: osc: Make osc_init() static Andreas Ruprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1423159299.4752.7.camel@perches.com \
--to=joe@perches.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=prabhakar.csengg@gmail.com \
--cc=rupran@einserver.de \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.