From: Joe Perches <joe@perches.com>
To: Murilo Opsfelder Araujo <mopsfelder@gmail.com>
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
jic23@kernel.org
Subject: Re: [PATCH 0/8] staging: iio: accel: multiple coding style fixes
Date: Thu, 31 Jul 2014 15:41:49 -0700 [thread overview]
Message-ID: <1406846509.9953.6.camel@joe-AO725> (raw)
In-Reply-To: <1406846098-19866-1-git-send-email-mopsfelder@gmail.com>
On Thu, 2014-07-31 at 19:34 -0300, Murilo Opsfelder Araujo wrote:
> The following patches fix (almost) all warnings reported by
> checkpatch.pl.
>
> Murilo Opsfelder Araujo (8):
> staging: iio: accel: adis16203_core.c: fix coding style
> staging: iio: accel: adis16201_core.c: fix coding style
> staging: iio: accel: adis16204_core.c: fix coding style
> staging: iio: accel: adis16209_core.c: fix coding style
> staging: iio: accel: adis16240_core.c: fix coding style
> staging: iio: accel: lis3l02dq_core.c: fix coding style
> staging: iio: accel: lis3l02dq_ring.c: fix coding style
> staging: iio: accel: sca3000_core.c: fix coding style
Hi.
Next time it might be better to use patch subjects like
staging: <subsystem> Add blank lines between declarations and code
because "fix coding style" really isn't very descriptive.
prev parent reply other threads:[~2014-07-31 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 22:34 Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 1/8] staging: iio: accel: adis16203_core.c: fix coding style Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 2/8] staging: iio: accel: adis16201_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 3/8] staging: iio: accel: adis16204_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 4/8] staging: iio: accel: adis16209_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 5/8] staging: iio: accel: adis16240_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 6/8] staging: iio: accel: lis3l02dq_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 7/8] staging: iio: accel: lis3l02dq_ring.c: " Murilo Opsfelder Araujo
2014-07-31 22:34 ` [PATCH 8/8] staging: iio: accel: sca3000_core.c: " Murilo Opsfelder Araujo
2014-07-31 22:41 ` Joe Perches [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=1406846509.9953.6.camel@joe-AO725 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mopsfelder@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
all inboxes | Powered by JetHome®