linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Miguel Robles <miguel.robles@farole.net>,
	knaack.h@gmx.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging: iio: resolver: Fix warning, statements should start on a tabstop
Date: Sun, 19 Mar 2017 11:07:28 +0000	[thread overview]
Message-ID: <b7dcb4e2-f393-26d1-f8c0-756be9d966c0@kernel.org> (raw)
In-Reply-To: <1489674509-9641-1-git-send-email-miguel.robles@farole.net>

On 16/03/17 14:28, Miguel Robles wrote:
> Fix checkpatch warning:
> Statements should start on a tabstop.
> 
> Signed-off-by: Miguel Robles <miguel.robles@farole.net>
Applied with the part name added to the patch title.

Jonathan
> ---
>  drivers/staging/iio/resolver/ad2s1210.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/iio/resolver/ad2s1210.c b/drivers/staging/iio/resolver/ad2s1210.c
> index 90b57c0..a6a8393 100644
> --- a/drivers/staging/iio/resolver/ad2s1210.c
> +++ b/drivers/staging/iio/resolver/ad2s1210.c
> @@ -490,8 +490,8 @@ static int ad2s1210_read_raw(struct iio_dev *indio_dev,
>  		ad2s1210_set_mode(MOD_VEL, st);
>  		break;
>  	default:
> -	       ret = -EINVAL;
> -	       break;
> +		ret = -EINVAL;
> +		break;
>  	}
>  	if (ret < 0)
>  		goto error_ret;
> 


      reply	other threads:[~2017-03-19 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 14:28 [PATCH] Staging: iio: resolver: Fix warning, statements should start on a tabstop Miguel Robles
2017-03-19 11:07 ` 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=b7dcb4e2-f393-26d1-f8c0-756be9d966c0@kernel.org \
    --to=jic23@kernel.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=miguel.robles@farole.net \
    --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).