From: Joe Perches <joe@perches.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>, Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>,
Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Minimize checkpatch induced patches...
Date: Wed, 14 Sep 2016 12:09:48 -0700 [thread overview]
Message-ID: <1473880188.32273.49.camel@perches.com> (raw)
In-Reply-To: <17f24fb7-6f69-63dd-d253-865509467717@de.ibm.com>
On Wed, 2016-09-14 at 20:54 +0200, Christian Borntraeger wrote:
> On 09/14/2016 08:33 PM, Greg KH wrote:
> > That's not true, I _WANT_ checkpatch cleanups for the portion of the
> > kernel I maintain. It keeps the code correct, up to date, easier to
> > maintain, and in doing so, we have found real bugs over time.
> Assuming that there are others with the same opinions that means that
> Joes patch is not the right solution?
The patch doesn't forbid that.
It just means any checkpatch induced change outside of
drivers/staging would generally be intentional and would not
commonly be submitted by inexperienced developers.
next prev parent reply other threads:[~2016-09-14 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 17:51 [PATCH] checkpatch: Minimize checkpatch induced patches Joe Perches
2016-09-14 17:56 ` Christian Borntraeger
2016-09-14 18:06 ` Joe Perches
2016-09-14 18:16 ` Christian Borntraeger
2016-09-14 18:21 ` Joe Perches
2016-09-14 18:24 ` Christian Borntraeger
2016-09-14 18:33 ` Greg KH
2016-09-14 18:54 ` Christian Borntraeger
2016-09-14 19:09 ` Joe Perches [this message]
2016-09-18 19:38 ` Christian Borntraeger
2016-09-14 23:54 ` Josh Triplett
2016-09-15 0:05 ` Joe Perches
2016-09-15 0:09 ` Josh Triplett
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=1473880188.32273.49.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=borntraeger@de.ibm.com \
--cc=corbet@lwn.net \
--cc=greg@kroah.com \
--cc=josh@joshtriplett.org \
--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