From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Sam Ravnborg <sam@ravnborg.org>,
Manish Katiyar <mkatiyar@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Remove errors caught by checkpatch.pl in kernel/kallsyms.c
Date: Mon, 16 Feb 2009 16:13:10 +0000 [thread overview]
Message-ID: <20090216161310.GV28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090216155023.GA4422@elte.hu>
On Mon, Feb 16, 2009 at 04:50:23PM +0100, Ingo Molnar wrote:
>
> * Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>
> > Ingo Molnar wrote:
> > > We routinely mention Sparse, lockdep, Coverity, Coccinelle, kmemleak,
> > > ftrace, kmemcheck and other tools as well when it motives to fix a bug
> > > or uncleanliness. [...] It is absolutely fine to
> > > mention checkpatch when it catches uncleanliness in code that already
> > > got merged. I dont understand your point.
> >
> > I wrote "don't mention checkpatch" but I really meant "think about what
> > the effect of the patch is and describe this".
>
> Are you arguing that in all those other cases the tools should not be
> mentioned either? I dont think that position is tenable.
Hell, yes. I'm sick and tired of "$DRIVER: fix sparse warnings <something
far off-screen when looking at it in mutt on xterm>" kind of subjects,
while we are at it. Mention the tool when that adds information useful for
understanding commit message and patch; otherwise you are just adding noise.
next prev parent reply other threads:[~2009-02-16 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 18:34 [PATCH] Remove errors caught by checkpatch.pl in kernel/kallsyms.c Manish Katiyar
2009-02-15 18:47 ` Sam Ravnborg
2009-02-15 18:47 ` Manish Katiyar
2009-02-16 13:07 ` Stefan Richter
2009-02-16 13:28 ` Ingo Molnar
2009-02-16 14:00 ` Stefan Richter
2009-02-16 14:19 ` Ingo Molnar
2009-02-16 15:22 ` Stefan Richter
2009-02-16 15:41 ` Manish Katiyar
2009-02-16 15:50 ` Ingo Molnar
2009-02-16 16:13 ` Stefan Richter
2009-02-16 17:12 ` Ingo Molnar
2009-02-16 18:04 ` Stefan Richter
2009-02-16 16:13 ` Al Viro [this message]
2009-02-16 17:11 ` Ingo Molnar
2009-02-16 14:28 ` Paolo Ciarrocchi
2009-02-16 16:17 ` Julia Lawall
2009-02-16 16:35 ` Stefan Richter
2009-02-16 17:21 ` Ingo Molnar
2009-02-16 17:15 ` Ingo Molnar
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=20090216161310.GV28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mkatiyar@gmail.com \
--cc=sam@ravnborg.org \
--cc=stefanr@s5r6.in-berlin.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox