From: Jonathan Cameron <jic23@kernel.org>
To: Colin King <colin.king@canonical.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: iio: adc: fix indent on break statement
Date: Sun, 24 Jan 2016 14:49:01 +0000 [thread overview]
Message-ID: <56A4E45D.5090900@kernel.org> (raw)
In-Reply-To: <1453577590-12177-1-git-send-email-colin.king@canonical.com>
On 23/01/16 19:33, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Fix indent warning when building with gcc 6:
> drivers/staging/iio/adc/ad7192.c:239:4: warning: statement is indented
> as if it were guarded by... [-Wmisleading-indentation]
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied to the togreg branch of iio.git - initially pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
> ---
> drivers/staging/iio/adc/ad7192.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/adc/ad7192.c b/drivers/staging/iio/adc/ad7192.c
> index 9221103..92f2b72 100644
> --- a/drivers/staging/iio/adc/ad7192.c
> +++ b/drivers/staging/iio/adc/ad7192.c
> @@ -236,7 +236,7 @@ static int ad7192_setup(struct ad7192_state *st,
> st->mclk = pdata->ext_clk_hz;
> else
> st->mclk = AD7192_INT_FREQ_MHZ;
> - break;
> + break;
> default:
> ret = -EINVAL;
> goto out;
>
prev parent reply other threads:[~2016-01-24 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 19:33 [PATCH] Staging: iio: adc: fix indent on break statement Colin King
2016-01-24 14:49 ` Jonathan Cameron [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=56A4E45D.5090900@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).