From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Holler <holler@ahsoftware.de>,
Joe Perches <joe@perches.com>, "Theodore Ts'o" <tytso@mit.edu>,
Andy Whitcroft <apw@shadowen.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] checkpatch: Find CamelCase definitions of struct/union/enum
Date: Wed, 25 Sep 2013 21:23:22 +0100 [thread overview]
Message-ID: <20130925202322.GB13318@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130925130352.0e89fd9439eff93c69cdcc32@linux-foundation.org>
On Wed, Sep 25, 2013 at 01:03:52PM -0700, Andrew Morton wrote:
> On Wed, 25 Sep 2013 21:54:49 +0200 Alexander Holler <holler@ahsoftware.de> wrote:
>
> > Am 25.09.2013 21:48, schrieb Joe Perches:
> >
> > > As I've said multiple times, checkpatch is a stupid
> > > little tool that can be ignored by anyone with
> > > different tastes.
> >
> > Just that this isn't true for ordinary innocent people posting patches.
>
> Nobody uses --strict. Discussion is silly.
That it is, but you are mistaken about nobody using --strict; I've been
amused a while ago by a patch (duly forwarded to Dave Null for processing,
of course) that "fixed" something like goto Efault, in I don't remember
which file ;-)
next prev parent reply other threads:[~2013-09-25 20:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 18:38 [PATCH] checkpatch: Find CamelCase definitions of struct/union/enum Joe Perches
2013-09-25 15:24 ` Al Viro
2013-09-25 15:35 ` Joe Perches
2013-09-25 16:19 ` Al Viro
2013-09-25 17:27 ` Alexander Holler
2013-09-25 19:22 ` Joe Perches
2013-09-25 19:30 ` Theodore Ts'o
2013-09-25 19:48 ` Joe Perches
2013-09-25 19:54 ` Alexander Holler
2013-09-25 20:03 ` Andrew Morton
2013-09-25 20:23 ` Al Viro [this message]
2013-09-26 1:10 ` Theodore Ts'o
2013-09-26 1:13 ` Andrew Morton
2013-09-25 20:11 ` Al Viro
2013-09-26 0:38 ` Joe Perches
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=20130925202322.GB13318@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=holler@ahsoftware.de \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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