public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, apw@shadowen.org,
	akpm@linux-foundation.org
Subject: Re: [PATCH] Deprecate checkpatch.pl --file
Date: Tue, 8 Jan 2008 18:53:47 +0100	[thread overview]
Message-ID: <20080108175347.GA25968@uranus.ravnborg.org> (raw)
In-Reply-To: <1199811033.1756.29.camel@imap.mvista.com>

On Tue, Jan 08, 2008 at 08:50:33AM -0800, Daniel Walker wrote:
> 
> On Tue, 2008-01-08 at 17:14 +0100, Andi Kleen wrote:
> 
> 
> > +if ($file) {
> > +	print <<EOL
> > +WARNING: Using --file mode. Please do not send patches to linux-kernel
> > +that change whole existing files if you did not significantly change most
> > +of the the file for other reasons anyways or just wrote the file newly
> > +from scratch. Pure code style patches have a significant cost in a
> > +quickly changing code base like Linux because they cause rejects
> > +with other changes.
> > +If you're sure you want to use whole file mode please use --file-force
> > +EOL
> > +;
> > +	exit(1);
> 
> Can't say I like this too much .. It sounds like your telling people to
> stop sending cleanup patches, which doesn't make much sense .. We want a
> clean kernel .. Or at least I do ..

It is a simple pain/benefit issue.
Fixing the 25 errors and 13 warnings in kernel/profile.c may look
like an easy task but then we put additional burden on the 10 people
that have patches pending for this file.

It is the same reason why we do not run a 'kill-trailing-whitespace'
on the full kernel tree.

	Sam

  reply	other threads:[~2008-01-08 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 16:14 [PATCH] Deprecate checkpatch.pl --file Andi Kleen
2008-01-08 16:50 ` Daniel Walker
2008-01-08 17:53   ` Sam Ravnborg [this message]
2008-01-08 18:01     ` Daniel Walker
2008-01-08 18:20       ` Theodore Tso
2008-01-08 18:33         ` Daniel Walker
2008-01-08 19:21           ` Sam Ravnborg
2008-01-08 19:27             ` Andi Kleen
2008-01-08 20:19             ` Daniel Walker
2008-01-08 21:14               ` Theodore Tso
2008-01-08 21:50                 ` Daniel Walker
2008-01-08 20:27     ` Bartlomiej Zolnierkiewicz

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=20080108175347.GA25968@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=apw@shadowen.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    /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