public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Joe Perches <joe@perches.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	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 15:30:35 -0400	[thread overview]
Message-ID: <20130925193035.GA11905@thunk.org> (raw)
In-Reply-To: <1380136920.17366.15.camel@joe-AO722>

On Wed, Sep 25, 2013 at 12:22:00PM -0700, Joe Perches wrote:
> 
> > 	* labels a-la Enomem, etc.  I've been using those and I will
> > keep doing so, checkpatch.pl and its users be damned.
> 
> Good on you.

I'm with Al.  This is just silly to add to checkpatch.

> Fine by me.  Don't use checkpatch.  No stress from me.

I still get some of your minions sending patches asking to "fix" ext4
from time to time.  It wastes everyone's time.

BTW, checkpatch barfs on pretty much everything in
linux/trace/events/*.h

						- Ted

  reply	other threads:[~2013-09-25 19:30 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 [this message]
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
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=20130925193035.GA11905@thunk.org \
    --to=tytso@mit.edu \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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