public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: 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 14:28:22 +0100	[thread overview]
Message-ID: <20090216132822.GC17996@elte.hu> (raw)
In-Reply-To: <4999650C.6030700@s5r6.in-berlin.de>


* Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:

> On 2/15/2009 7:47 PM, Sam Ravnborg wrote:
> > On Mon, Feb 16, 2009 at 12:04:36AM +0530, Manish Katiyar wrote:
> >> Hi Ingo,
> >> 
> >> I used your code-quality script to do cleanup in kernel/kallsyms.c.
> >> Below patch removes errors generated by checkpatch.pl.
> > When doing so use checkpatch only as a hint generator and do
> > not concentrate only on the warnings/errors generated by checkpatch.
> > 
> > Your patch is an improvement but please fix the remaining issues.
> 
> Furthermore, the changelog is bad (non-exiting in fact).
> 
> The fact that the issues where discovered using checkpatch is absolutely
> uninteresting.  The changelog should describe /what/ is fixed, e.g.
> whitespace, maybe other things.  (In case of nontrivial changes the log
> may also need to explain not only the /what but also the /how/, but this
> does not apply to patches like this one.)

The commit log definitely needs enhancements but it's not uninteresting 
at all what tools were used to arrive to a change. It shouldnt be in the 
title, but can be mentioned in the changelog itself. (and should be 
mentioned if the cleanup ever gets as far as the mainline kernel - if a 
good and acceptable commit results out of a tool's usage then that tool 
needs to be advertised some more.)

Nevertheless i think that these cleanups need to go a bit wider than 
just the issues pointed, as i described it in the related 
kernel/signal.c thread.

	Ingo

  reply	other threads:[~2009-02-16 13:28 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 [this message]
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
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=20090216132822.GC17996@elte.hu \
    --to=mingo@elte.hu \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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