linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: jic23@cam.ac.uk, marex@denx.de, linux-iio@vger.kernel.org,
	Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH 1/2] iio: mxs-lradc: Fix the order of resources removal
Date: Sun, 08 Sep 2013 15:29:27 +0100	[thread overview]
Message-ID: <522C89C7.1010106@kernel.org> (raw)
In-Reply-To: <1378169292-29899-1-git-send-email-festevam@gmail.com>

On 09/03/13 01:48, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
> 
> Fix the order of resources removal in the error path of mxs_lradc_probe()
> and also in mxs_lradc_remove().
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
I 'think' this bug could cause actual trouble but I'll assume it is relatively unlikely
and have applied this to the togreg branch of iio.git (won't apply to the current fixes
branch).

Anyhow, applied to the togreg branch of iio.git

> ---
>  drivers/staging/iio/adc/mxs-lradc.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/staging/iio/adc/mxs-lradc.c b/drivers/staging/iio/adc/mxs-lradc.c
> index a08c173..75f5aac 100644
> --- a/drivers/staging/iio/adc/mxs-lradc.c
> +++ b/drivers/staging/iio/adc/mxs-lradc.c
> @@ -987,7 +987,7 @@ static int mxs_lradc_probe(struct platform_device *pdev)
>  	/* Register the touchscreen input device. */
>  	ret = mxs_lradc_ts_register(lradc);
>  	if (ret)
> -		goto err_dev;
> +		goto err_ts_register;
>  
>  	/* Register IIO device. */
>  	ret = iio_device_register(iio);
> @@ -1000,6 +1000,8 @@ static int mxs_lradc_probe(struct platform_device *pdev)
>  
>  err_ts:
>  	mxs_lradc_ts_unregister(lradc);
> +err_ts_register:
> +	mxs_lradc_hw_stop(lradc);
>  err_dev:
>  	mxs_lradc_trigger_remove(iio);
>  err_trig:
> @@ -1012,13 +1014,11 @@ static int mxs_lradc_remove(struct platform_device *pdev)
>  	struct iio_dev *iio = platform_get_drvdata(pdev);
>  	struct mxs_lradc *lradc = iio_priv(iio);
>  
> +	iio_device_unregister(iio);
>  	mxs_lradc_ts_unregister(lradc);
> -
>  	mxs_lradc_hw_stop(lradc);
> -
> -	iio_device_unregister(iio);
> -	iio_triggered_buffer_cleanup(iio);
>  	mxs_lradc_trigger_remove(iio);
> +	iio_triggered_buffer_cleanup(iio);
>  
>  	return 0;
>  }
> 

      parent reply	other threads:[~2013-09-08 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03  0:48 [PATCH 1/2] iio: mxs-lradc: Fix the order of resources removal Fabio Estevam
2013-09-03  0:48 ` [PATCH 2/2] iio: mxs-lradc: Add MODULE_ALIAS Fabio Estevam
2013-09-03  0:59   ` Marek Vasut
2013-09-08 14:31     ` Jonathan Cameron
2013-09-08 14:52       ` Fabio Estevam
2013-09-08 15:00         ` Marek Vasut
2013-09-08 15:33           ` Jonathan Cameron
2013-09-08 16:11             ` Marek Vasut
2013-09-08 17:03               ` Jonathan Cameron
2013-09-08 18:47                 ` Fabio Estevam
2013-09-03  1:00 ` [PATCH 1/2] iio: mxs-lradc: Fix the order of resources removal Marek Vasut
2013-09-08 14:29 ` 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=522C89C7.1010106@kernel.org \
    --to=jic23@kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=jic23@cam.ac.uk \
    --cc=linux-iio@vger.kernel.org \
    --cc=marex@denx.de \
    /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).