public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mircea Caprioru <mircea.caprioru@analog.com>
Cc: <Michael.Hennerich@analog.com>, <lars@metafoo.de>,
	<gregkh@linuxfoundation.org>, <linux-kernel@vger.kernel.org>,
	<linux-iio@vger.kernel.org>
Subject: Re: [PATCH 2/2] staging: iio: adc: ad7192: Report error directly in ad7192_setup
Date: Sat, 16 Mar 2019 16:45:19 +0000	[thread overview]
Message-ID: <20190316164519.5faf1238@archlinux> (raw)
In-Reply-To: <20190315111425.14275-2-mircea.caprioru@analog.com>

On Fri, 15 Mar 2019 13:14:25 +0200
Mircea Caprioru <mircea.caprioru@analog.com> wrote:

> This patch removes the goto out statement thus ensuring that an error is
> report as soon as it occurs. This gives more information and improves
> readability.
No problem with the patch, but I'm not sure why it gives more information?
Gone from printing an useless error message to printing none.

I'll just drop that bit of the description in favour of code readability.
Hope you don't mind!

Jonathan
> 
> Signed-off-by: Mircea Caprioru <mircea.caprioru@analog.com>
> ---
>  drivers/staging/iio/adc/ad7192.c | 13 +++++--------
>  1 file changed, 5 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/staging/iio/adc/ad7192.c b/drivers/staging/iio/adc/ad7192.c
> index ebab75bdeed7..27f962b8c4ef 100644
> --- a/drivers/staging/iio/adc/ad7192.c
> +++ b/drivers/staging/iio/adc/ad7192.c
> @@ -236,13 +236,13 @@ static int ad7192_setup(struct ad7192_state *st,
>  	/* reset the serial interface */
>  	ret = ad_sd_reset(&st->sd, 48);
>  	if (ret < 0)
> -		goto out;
> +		return ret;
>  	usleep_range(500, 1000); /* Wait for at least 500us */
>  
>  	/* write/read test for device presence */
>  	ret = ad_sd_read_reg(&st->sd, AD7192_REG_ID, 1, &id);
>  	if (ret)
> -		goto out;
> +		return ret;
>  
>  	id &= AD7192_ID_MASK;
>  
> @@ -310,15 +310,15 @@ static int ad7192_setup(struct ad7192_state *st,
>  
>  	ret = ad_sd_write_reg(&st->sd, AD7192_REG_MODE, 3, st->mode);
>  	if (ret)
> -		goto out;
> +		return ret;
>  
>  	ret = ad_sd_write_reg(&st->sd, AD7192_REG_CONF, 3, st->conf);
>  	if (ret)
> -		goto out;
> +		return ret;
>  
>  	ret = ad7192_calibrate_all(st);
>  	if (ret)
> -		goto out;
> +		return ret;
>  
>  	/* Populate available ADC input ranges */
>  	for (i = 0; i < ARRAY_SIZE(st->scale_avail); i++) {
> @@ -332,9 +332,6 @@ static int ad7192_setup(struct ad7192_state *st,
>  	}
>  
>  	return 0;
> -out:
> -	dev_err(&st->sd.spi->dev, "setup failed\n");
> -	return ret;
>  }
>  
>  static ssize_t


  reply	other threads:[~2019-03-16 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 11:14 [PATCH 1/2] staging: iio: adc: ad7192: Fix identation Mircea Caprioru
2019-03-15 11:14 ` [PATCH 2/2] staging: iio: adc: ad7192: Report error directly in ad7192_setup Mircea Caprioru
2019-03-16 16:45   ` Jonathan Cameron [this message]
2019-03-16 16:52     ` Jonathan Cameron
2019-03-16 16:39 ` [PATCH 1/2] staging: iio: adc: ad7192: Fix identation 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=20190316164519.5faf1238@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mircea.caprioru@analog.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