From: Dan Carpenter <dan.carpenter@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: Evan Hosseini <hosse005@umn.edu>,
lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
knaack.h@gmx.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: iio: Fix some character line limit coding style issues
Date: Sat, 7 Nov 2015 23:40:19 +0300 [thread overview]
Message-ID: <20151107204019.GQ7289@mwanda> (raw)
In-Reply-To: <1446919324.2701.1.camel@perches.com>
On Sat, Nov 07, 2015 at 10:02:04AM -0800, Joe Perches wrote:
> On Sat, 2015-11-07 at 19:30 +0300, Dan Carpenter wrote:
> > The original is easier to read, sorry. Checkpatch is a tool not the
> > king of the world to obeyed at all times.
>
> Completely agree.
>
> Perhaps there could be some comment indicators added
> to tell checkpatch to ignore certain warnings like
> 80 columns.
Applying or rejecting this patch was an easy call so it doesn't cause
decision fatigue or drain my emotions. I feel like these patches are
instructional so people learn not to trust tools. Checkpatch.pl is fine
as-is.
regards,
dan carpenter
prev parent reply other threads:[~2015-11-07 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 15:06 [PATCH] Staging: iio: Fix some character line limit coding style issues Evan Hosseini
2015-11-07 16:30 ` Dan Carpenter
2015-11-07 18:02 ` Joe Perches
2015-11-07 20:40 ` Dan Carpenter [this message]
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=20151107204019.GQ7289@mwanda \
--to=dan.carpenter@oracle.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hosse005@umn.edu \
--cc=jic23@kernel.org \
--cc=joe@perches.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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