linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH V2] gpio: of: make example syntactically correct
Date: Wed, 27 Dec 2017 08:48:39 +0100	[thread overview]
Message-ID: <20171227074839.GC15612@bigcity.dyn.berto.se> (raw)
In-Reply-To: <20171223200641.3709-1-wsa+renesas@sang-engineering.com>

Hi Wolfram,

Thanks for your patch.

On 2017-12-23 21:06:41 +0100, Wolfram Sang wrote:
> The ';' was missing. And cosmetic: there was a space too much.
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>

> ---
> 
> Changes since V1:
> * removed extra spaces (Thanks Sergei!)
> 
>  Documentation/devicetree/bindings/gpio/gpio.txt | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt b/Documentation/devicetree/bindings/gpio/gpio.txt
> index 802402f6cc5d89..bc5fe95d33fff0 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio.txt
> +++ b/Documentation/devicetree/bindings/gpio/gpio.txt
> @@ -33,12 +33,12 @@ The following example could be used to describe GPIO pins used as device enable
>  and bit-banged data signals:
>  
>  	gpio1: gpio1 {
> -		gpio-controller
> -		 #gpio-cells = <2>;
> +		gpio-controller;
> +		#gpio-cells = <2>;
>  	};
>  	gpio2: gpio2 {
> -		gpio-controller
> -		 #gpio-cells = <1>;
> +		gpio-controller;
> +		#gpio-cells = <1>;
>  	};
>  	[...]
>  
> -- 
> 2.11.0
> 

-- 
Regards,
Niklas Söderlund

      reply	other threads:[~2017-12-27  7:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-23 20:06 [PATCH V2] gpio: of: make example syntactically correct Wolfram Sang
2017-12-27  7:48 ` Niklas Söderlund [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=20171227074839.GC15612@bigcity.dyn.berto.se \
    --to=niklas.soderlund@ragnatech.se \
    --cc=geert@linux-m68k.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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).