devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: swarren@nvidia.com, mark.rutland@arm.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	dwillemsen@nvidia.com
Subject: Re: [PATCH] dt-binding: mfd: as3722: correct macro name
Date: Tue, 17 Jun 2014 21:11:15 +0100	[thread overview]
Message-ID: <20140617201115.GV29841@lee--X1> (raw)
In-Reply-To: <1402302719-9766-1-git-send-email-ldewangan@nvidia.com>

On Mon, 09 Jun 2014, Laxman Dewangan wrote:

> The macro name for enable3 pin is named as AS3722_EXT_CONTROL_PIN_ENABLE2
> which is conflict with the enable2 pin.
> 
> Correct this macro name to correctly reflect the enable pin i.e.
> AS3722_EXT_CONTROL_PIN_ENABLE3.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> Reported-by: Dan Willemsen <dwillemsen@nvidia.com>
> ---
>  include/dt-bindings/mfd/as3722.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied, thanks.

> diff --git a/include/dt-bindings/mfd/as3722.h b/include/dt-bindings/mfd/as3722.h
> index 0e69256..e66c089 100644
> --- a/include/dt-bindings/mfd/as3722.h
> +++ b/include/dt-bindings/mfd/as3722.h
> @@ -13,7 +13,7 @@
>  /* External control pins */
>  #define AS3722_EXT_CONTROL_PIN_ENABLE1 1
>  #define AS3722_EXT_CONTROL_PIN_ENABLE2 2
> -#define AS3722_EXT_CONTROL_PIN_ENABLE2 3
> +#define AS3722_EXT_CONTROL_PIN_ENABLE3 3
>  
>  /* Interrupt numbers for AS3722 */
>  #define AS3722_IRQ_LID			0

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2014-06-17 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  8:31 [PATCH] dt-binding: mfd: as3722: correct macro name Laxman Dewangan
2014-06-17 20:11 ` Lee Jones [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=20140617201115.GV29841@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dwillemsen@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=swarren@nvidia.com \
    /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).