public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Richard Weinberger <richard@nod.at>
Cc: Borislav Petkov <bp@suse.de>,
	akpm@linux-foundation.org, apw@canonical.com, joe@perches.com,
	tytso@mit.edu, dwalter@google.com, neilb@suse.de,
	hch@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch.pl: Remove --file option
Date: Fri, 18 Jul 2014 06:56:12 -0700	[thread overview]
Message-ID: <20140718135612.GA18432@roeck-us.net> (raw)
In-Reply-To: <53C92535.2010605@nod.at>

On Fri, Jul 18, 2014 at 03:46:29PM +0200, Richard Weinberger wrote:
> Am 18.07.2014 15:37, schrieb Guenter Roeck:
> > On 07/18/2014 01:23 AM, Borislav Petkov wrote:
> >> On Fri, Jul 18, 2014 at 12:29:37AM -0700, Guenter Roeck wrote:
> >>> First, 'abuse' is a relative term. It describes a use you
> >>> (and possibly many others) may find objectionable, but that
> >>> does not mean all uses are objectionable.
> >>
> >> Do you actually have a valid use case for keeping the cmdline switch ...
> >>
> > 
> > I find it convenient to be able to check a new file before committing it
> > and creating a patch. Also, I find it convenient to be able use it to clean
> > up a file before I do heavy lifting with it. Yes, I understand the latter
> > is discouraged nowadays, and I would not use it anymore outside my scope
> > of responsibility unless specifically asked by the maintainer to do so,
> > but in such cases it helps me a lot to be able to address the cleanup
> > prior to the heavy lifting.
> 
> As capable kernel hacker you can still use a command like:
> diff -urN /dev/null $file | ./scripts/checkpatch.pl -
> 

Yes, that came up before. Or I can revert the patch locally, or keep an old
version of checkpatch around. You make me suffer because someone else abuses
the system. That someone will find other ways to abuse the system, such as
using the same approach, or annoy you with something else, such as searching
for "fixme" statements in the code or sending unhelpful emails about failing
builds. The one thing you will not accomplish is to solve the problem.

Guenter

  reply	other threads:[~2014-07-18 13:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 15:34 [PATCH] checkpatch.pl: Remove --file option Richard Weinberger
2014-07-17 15:38 ` Borislav Petkov
2014-07-17 15:51 ` Joe Perches
2014-07-17 16:02   ` Borislav Petkov
2014-07-17 16:24     ` Joe Perches
2014-07-22  5:27     ` Kalle Valo
2014-08-04 14:30       ` Pavel Machek
2014-07-17 22:43   ` Thomas Gleixner
2014-07-18  7:29 ` Guenter Roeck
2014-07-18  8:23   ` Borislav Petkov
2014-07-18 13:37     ` Guenter Roeck
2014-07-18 13:46       ` Richard Weinberger
2014-07-18 13:56         ` Guenter Roeck [this message]
2014-07-18 14:22           ` Borislav Petkov
2014-07-18 14:21         ` Christoph Hellwig
2014-07-18 14:27           ` Borislav Petkov
2014-07-18 14:43             ` Guenter Roeck
2014-07-18 14:56               ` Borislav Petkov
2014-07-18 14:17 ` Lars-Peter Clausen
2014-07-18 14:24   ` Borislav Petkov
2014-07-18 14:35     ` Joe Perches
2014-07-18 14:49       ` Borislav Petkov
2014-07-18 14:57         ` Joe Perches
2014-07-18 15:06           ` Borislav Petkov

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=20140718135612.GA18432@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=bp@suse.de \
    --cc=dwalter@google.com \
    --cc=hch@infradead.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=richard@nod.at \
    --cc=tytso@mit.edu \
    /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