From: Jonathan Cameron <jic23@kernel.org>
To: Slawomir Stepien <sst@poczta.fm>, knaack.h@gmx.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 03/10] iio: adc: vf610_adc: fix case label indent
Date: Sat, 16 Apr 2016 13:31:49 +0100 [thread overview]
Message-ID: <571230B5.1040207@kernel.org> (raw)
In-Reply-To: <1460662602-2951-4-git-send-email-sst@poczta.fm>
On 14/04/16 20:36, Slawomir Stepien wrote:
> This fixes the error reported by checkpatch.pl:
>
> ERROR: switch and case should be at the same indent
>
> Signed-off-by: Slawomir Stepien <sst@poczta.fm>
Applied.
Thanks,
Jonathan
> ---
> drivers/iio/adc/vf610_adc.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/iio/adc/vf610_adc.c b/drivers/iio/adc/vf610_adc.c
> index b10f629..653bf13 100644
> --- a/drivers/iio/adc/vf610_adc.c
> +++ b/drivers/iio/adc/vf610_adc.c
> @@ -714,19 +714,19 @@ static int vf610_write_raw(struct iio_dev *indio_dev,
> int i;
>
> switch (mask) {
> - case IIO_CHAN_INFO_SAMP_FREQ:
> - for (i = 0;
> - i < ARRAY_SIZE(info->sample_freq_avail);
> - i++)
> - if (val == info->sample_freq_avail[i]) {
> - info->adc_feature.sample_rate = i;
> - vf610_adc_sample_set(info);
> - return 0;
> - }
> - break;
> + case IIO_CHAN_INFO_SAMP_FREQ:
> + for (i = 0;
> + i < ARRAY_SIZE(info->sample_freq_avail);
> + i++)
> + if (val == info->sample_freq_avail[i]) {
> + info->adc_feature.sample_rate = i;
> + vf610_adc_sample_set(info);
> + return 0;
> + }
> + break;
>
> - default:
> - break;
> + default:
> + break;
> }
>
> return -EINVAL;
>
next prev parent reply other threads:[~2016-04-16 12:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 19:36 [PATCH 00/10] iio: fix errors reported by checkpatch.pl Slawomir Stepien
2016-04-14 19:36 ` [PATCH 01/10] iio: light apds9960: fix wrong use of brace Slawomir Stepien
2016-04-14 23:29 ` Matt Ranostay
2016-04-15 14:56 ` Slawomir Stepien
2016-04-16 9:48 ` Dan Carpenter
2016-04-16 12:30 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 02/10] iio: inkern: add a missing space before if Slawomir Stepien
2016-04-16 12:31 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 03/10] iio: adc: vf610_adc: fix case label indent Slawomir Stepien
2016-04-16 12:31 ` Jonathan Cameron [this message]
2016-04-14 19:36 ` [PATCH 04/10] iio: adc: mcp3422: remove spaces before comma Slawomir Stepien
2016-04-16 12:32 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 05/10] iio: adc: at91_adc: fix errors reported by checkpatch.pl Slawomir Stepien
2016-04-16 12:33 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 06/10] iio: adc: ad799x: remove space before comma Slawomir Stepien
2016-04-16 12:34 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 07/10] iio: common: ms_sensors: use tab for indention Slawomir Stepien
2016-04-16 12:34 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 08/10] iio: common: hid-sensors: " Slawomir Stepien
2016-04-16 12:35 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 09/10] iio: magnetometer: ak8975: put else and brace at the same line Slawomir Stepien
2016-04-16 12:35 ` Jonathan Cameron
2016-04-14 19:36 ` [PATCH 10/10] iio: pressure: ms5611: use tab for indention Slawomir Stepien
2016-04-16 12:40 ` Jonathan Cameron
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=571230B5.1040207@kernel.org \
--to=jic23@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sst@poczta.fm \
/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).