From: Bryan Wu <cooloney@gmail.com>
To: Pramod Gurav <pramod.gurav@smartplayin.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 2/2] led: remove use of gpiochip_remove() retval
Date: Tue, 30 Sep 2014 14:21:45 -0700 [thread overview]
Message-ID: <CAK5ve-KCYHySjs4f+rd+kAvKQmTkJqsq87Muq_j-D0nB7WSYjQ@mail.gmail.com> (raw)
In-Reply-To: <1412087707-8313-1-git-send-email-pramod.gurav@smartplayin.com>
On Tue, Sep 30, 2014 at 7:35 AM, Pramod Gurav
<pramod.gurav@smartplayin.com> wrote:
> Get rid of using return value from gpiochip_remove() as it returns
> void.
>
Looks good to me. I will merge it.
But what's in the first patch. I just got this second patch in my email inbox.
-Bryan
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Alexandre Courbot <gnurou@gmail.com>
> Cc: Bryan Wu <cooloney@gmail.com>
> Cc: Richard Purdie <rpurdie@rpsys.net>
> Cc: linux-leds@vger.kernel.org
>
> Cc: linux-gpio@vger.kernel.org
>
> Signed-off-by: Pramod Gurav <pramod.gurav@smartplayin.com>
> ---
> drivers/leds/leds-pca9532.c | 10 ++--------
> drivers/leds/leds-tca6507.c | 7 ++-----
> 2 files changed, 4 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/leds/leds-pca9532.c b/drivers/leds/leds-pca9532.c
> index 4a0e786..5a6363d 100644
> --- a/drivers/leds/leds-pca9532.c
> +++ b/drivers/leds/leds-pca9532.c
> @@ -319,14 +319,8 @@ static int pca9532_destroy_devices(struct pca9532_data *data, int n_devs)
> }
>
> #ifdef CONFIG_LEDS_PCA9532_GPIO
> - if (data->gpio.dev) {
> - int err = gpiochip_remove(&data->gpio);
> - if (err) {
> - dev_err(&data->client->dev, "%s failed, %d\n",
> - "gpiochip_remove()", err);
> - return err;
> - }
> - }
> + if (data->gpio.dev)
> + gpiochip_remove(&data->gpio);
> #endif
>
> return 0;
> diff --git a/drivers/leds/leds-tca6507.c b/drivers/leds/leds-tca6507.c
> index 3d9e267..20fa8e7 100644
> --- a/drivers/leds/leds-tca6507.c
> +++ b/drivers/leds/leds-tca6507.c
> @@ -667,11 +667,8 @@ static int tca6507_probe_gpios(struct i2c_client *client,
>
> static void tca6507_remove_gpio(struct tca6507_chip *tca)
> {
> - if (tca->gpio.ngpio) {
> - int err = gpiochip_remove(&tca->gpio);
> - dev_err(&tca->client->dev, "%s failed, %d\n",
> - "gpiochip_remove()", err);
> - }
> + if (tca->gpio.ngpio)
> + gpiochip_remove(&tca->gpio);
> }
> #else /* CONFIG_GPIOLIB */
> static int tca6507_probe_gpios(struct i2c_client *client,
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2014-09-30 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 14:35 [PATCH 2/2] led: remove use of gpiochip_remove() retval Pramod Gurav
2014-09-30 21:21 ` Bryan Wu [this message]
2014-10-02 7:12 ` Linus Walleij
2014-10-03 17:15 ` Bryan Wu
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=CAK5ve-KCYHySjs4f+rd+kAvKQmTkJqsq87Muq_j-D0nB7WSYjQ@mail.gmail.com \
--to=cooloney@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pramod.gurav@smartplayin.com \
--cc=rpurdie@rpsys.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).