All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	linux-leds@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] leds: gpio: Use GPIOF_OUT_INIT_LOW instead of hardcoded zero
Date: Fri, 19 Feb 2016 16:29:01 +0100	[thread overview]
Message-ID: <56C734BD.8040209@samsung.com> (raw)
In-Reply-To: <1455875554-4268-1-git-send-email-geert+renesas@glider.be>

Hi Geert,

On 02/19/2016 10:52 AM, Geert Uytterhoeven wrote:
> Use the GPIO flag definition instead of a numeric literal, so the casual
> reader grepping for GPIOF_ will find the GPIO flags used.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>   drivers/leds/leds-gpio.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
> index 7bc53280dbfdd91d..89955574430cec75 100644
> --- a/drivers/leds/leds-gpio.c
> +++ b/drivers/leds/leds-gpio.c
> @@ -86,7 +86,7 @@ static int create_gpio_led(const struct gpio_led *template,
>   		 * still uses GPIO numbers. Ultimately we would like to get
>   		 * rid of this block completely.
>   		 */
> -		unsigned long flags = 0;
> +		unsigned long flags = GPIOF_OUT_INIT_LOW;
>
>   		/* skip leds that aren't available */
>   		if (!gpio_is_valid(template->gpio)) {
>

Applied, thanks.

-- 
Best regards,
Jacek Anaszewski

      reply	other threads:[~2016-02-19 15:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19  9:52 [PATCH] leds: gpio: Use GPIOF_OUT_INIT_LOW instead of hardcoded zero Geert Uytterhoeven
2016-02-19 15:29 ` Jacek Anaszewski [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=56C734BD.8040209@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=geert+renesas@glider.be \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.