linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: linux-iio@vger.kernel.org, Akinobu Mita <akinobu.mita@gmail.com>,
	Crestez Dan Leonard <leonard.crestez@intel.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] iio/light/max44000: Use common error handling code in max44000_probe()
Date: Thu, 26 Oct 2017 17:29:26 +0100	[thread overview]
Message-ID: <20171026172926.62d5ff87@archlinux> (raw)
In-Reply-To: <28854212-d360-8636-4de5-017fbee0db36@users.sourceforge.net>

On Thu, 26 Oct 2017 10:40:12 +0200
SF Markus Elfring <elfring@users.sourceforge.net> wrote:

> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Thu, 26 Oct 2017 10:30:57 +0200
> 
> * Add a jump target so that a specific error message is stored only once
>   at the end of this function implementation.
> 
> * Replace two calls of the function "dev_err" by goto statements.
> 
> * Adjust condition checks.
> 
> This issue was detected by using the Coccinelle software.
> 
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>

Again, throttle your patch sending please Markus as it will save
everyone time.  I try to give full reasoning in each patch because
others may encounter them without having visibility of similar
patches posted at the same time.  As such I end up writing
the same thing multiple times wasting my time on top of the time
you have already wasted by sending out multiple patches of a type
I am going to reject..

> ---
>  drivers/iio/light/max44000.c | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/iio/light/max44000.c b/drivers/iio/light/max44000.c
> index bcdb0eb9e537..8f4bc6a918d5 100644
> --- a/drivers/iio/light/max44000.c
> +++ b/drivers/iio/light/max44000.c
> @@ -569,18 +569,14 @@ static int max44000_probe(struct i2c_client *client,
>  	 * Set a middle value so that we get some sort of valid data by default.
>  	 */
>  	ret = max44000_write_led_current_raw(data, MAX44000_LED_CURRENT_DEFAULT);
> -	if (ret < 0) {
> -		dev_err(&client->dev, "failed to write init config: %d\n", ret);
> -		return ret;
> -	}
> +	if (ret)
> +		goto report_failure;
>  
>  	/* Reset CFG bits to ALS_PRX mode which allows easy reading of both values. */
>  	reg = MAX44000_CFG_TRIM | MAX44000_CFG_MODE_ALS_PRX;
>  	ret = regmap_write(data->regmap, MAX44000_REG_CFG_MAIN, reg);
> -	if (ret < 0) {
> -		dev_err(&client->dev, "failed to write init config: %d\n", ret);
> -		return ret;
> -	}
> +	if (ret)
> +		goto report_failure;
>  
>  	/* Read status at least once to clear any stale interrupt bits. */
>  	ret = regmap_read(data->regmap, MAX44000_REG_STATUS, &reg);
> @@ -596,6 +592,10 @@ static int max44000_probe(struct i2c_client *client,
>  	}
>  
>  	return iio_device_register(indio_dev);
> +
> +report_failure:
> +	dev_err(&client->dev, "failed to write init config: %d\n", ret);
This reduces readability of the code for a very minor gain.  
Printing an error message is not a source of bugs or similar unlike
unwinding some state, so a unified path makes little sense. 


> +	return ret;
>  }
>  
>  static int max44000_remove(struct i2c_client *client)


  reply	other threads:[~2017-10-26 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  8:40 [PATCH] iio/light/max44000: Use common error handling code in max44000_probe() SF Markus Elfring
2017-10-26 16:29 ` Jonathan Cameron [this message]
2017-10-26 16:50   ` SF Markus Elfring
2017-10-26 17:39     ` 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=20171026172926.62d5ff87@archlinux \
    --to=jic23@kernel.org \
    --cc=akinobu.mita@gmail.com \
    --cc=elfring@users.sourceforge.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=leonard.crestez@intel.com \
    --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).