From: Davidlohr Bueso <davidlohr@hp.com>
To: Nick Krause <xerofoify@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Richard Henderson <rth@twiddle.net>,
ink@jurassic.park.msu.ru, Matt Turner <mattst88@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
linux-alpha@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: Alpha Checkpatch Errors
Date: Thu, 17 Jul 2014 20:21:33 -0700 [thread overview]
Message-ID: <1405653693.21735.9.camel@buesod1.americas.hpqcorp.net> (raw)
In-Reply-To: <CAPDOMViHhE22ndcjez+vfZWGprsx_Cw0Rn-FpaoNsi63cRnr9g@mail.gmail.com>
On Thu, 2014-07-17 at 23:01 -0400, Nick Krause wrote:
> On Thu, Jul 17, 2014 at 6:17 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > On Thu, 17 Jul 2014, Nick Krause wrote:
> >
> >> Hey Richard and other Maintainers,
> >> I am wondering about cleaning up the cleanpatch errors for alpha, as
> >> I am hitting a lot of in the arch/alpha directory.
> >> It would be nice if I got a list of files that still need coding style
> >> cleanup as this may be of nice to cleanup :).
> >
> > Nick, can you please stop that nonsense? checkpatch.pl is a tool to
> > check PATCHES and not to apply random nonsense on existing code. See
> > also:
> >
> > https://lwn.net/Articles/605597/
> >
> > Joe, can you please finally remove the -f option from checkpatch.pl ?
> >
> > Thanks,
> >
> > tglx
> I understand how about checkpatch. We should remove the -f option as I
> agree it gets used too much.
> Sorry Nick
Nick, are you human?
next prev parent reply other threads:[~2014-07-18 3:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 22:03 Alpha Checkpatch Errors Nick Krause
2014-07-17 22:17 ` Thomas Gleixner
2014-07-18 3:01 ` Nick Krause
2014-07-18 3:21 ` Davidlohr Bueso [this message]
2014-07-18 3:24 ` Nick Krause
2014-07-18 8:55 ` Borislav Petkov
2014-07-18 10:18 ` Peter Zijlstra
2014-07-18 11:58 ` Steven Rostedt
2014-07-18 17:08 ` Nick Krause
2014-07-18 17:31 ` Steven Rostedt
2014-07-18 17:35 ` Nick Krause
2014-07-18 17:50 ` Steven Rostedt
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=1405653693.21735.9.camel@buesod1.americas.hpqcorp.net \
--to=davidlohr@hp.com \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=joe@perches.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rth@twiddle.net \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xerofoify@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).