linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben@simtec.co.uk>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	spi-devel-general@lists.sourceforge.net
Subject: Re: [PATCH] spi: tle620x: add missing device_remove_file()
Date: Thu, 12 May 2011 09:25:41 +0100	[thread overview]
Message-ID: <4DCB9985.2050100@simtec.co.uk> (raw)
In-Reply-To: <1305117545.6324.3.camel@phoenix>

On 11/05/11 13:39, Axel Lin wrote:
> This patch includes below fixes:
> 1. Add missing device_remove_file for dev_attr_status_show in tle62x0_remove.
> 2. Fix tle62x0_probe error handling:
>     Currently, if the error happens when ptr>  0, gpio_attrs[0] is not
>     properly remove.
>
> Signed-off-by: Axel Lin<axel.lin@gmail.com>
Acked-by: Ben Dooks <ben-linux@fluff.org>
> ---
>   drivers/spi/tle62x0.c |    3 ++-
>   1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/spi/tle62x0.c b/drivers/spi/tle62x0.c
> index a393895..32a4087 100644
> --- a/drivers/spi/tle62x0.c
> +++ b/drivers/spi/tle62x0.c
> @@ -283,7 +283,7 @@ static int __devinit tle62x0_probe(struct spi_device *spi)
>   	return 0;
>
>    err_gpios:
> -	for (; ptr>  0; ptr--)
> +	while (--ptr>= 0)
>   		device_remove_file(&spi->dev, gpio_attrs[ptr]);
>
>   	device_remove_file(&spi->dev,&dev_attr_status_show);
> @@ -301,6 +301,7 @@ static int __devexit tle62x0_remove(struct spi_device *spi)
>   	for (ptr = 0; ptr<  st->nr_gpio; ptr++)
>   		device_remove_file(&spi->dev, gpio_attrs[ptr]);
>
> +	device_remove_file(&spi->dev,&dev_attr_status_show);
>   	kfree(st);
>   	return 0;
>   }

  reply	other threads:[~2011-05-12  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 12:39 [PATCH] spi: tle620x: add missing device_remove_file() Axel Lin
2011-05-12  8:25 ` Ben Dooks [this message]
2011-05-27  3:31   ` Grant Likely

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=4DCB9985.2050100@simtec.co.uk \
    --to=ben@simtec.co.uk \
    --cc=axel.lin@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.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).