All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Marek Vasut <marex@denx.de>
Cc: linux-doc@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] LED: Fix missing semicolon in OF documentation
Date: Sun, 24 Jun 2012 01:49:44 -0500	[thread overview]
Message-ID: <4FE6B888.1090700@landley.net> (raw)
In-Reply-To: <1340476877-2704-1-git-send-email-marex@denx.de>

On 06/23/2012 01:41 PM, Marek Vasut wrote:
> Trivial fix
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Cc: Rob Herring <rob.herring@calxeda.com>
> Cc: Rob Landley <rob@landley.net>
> Cc: devicetree-discuss@lists.ozlabs.org
> Cc: linux-doc@vger.kernel.org
> ---
>  Documentation/devicetree/bindings/gpio/led.txt |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/gpio/led.txt b/Documentation/devicetree/bindings/gpio/led.txt
> index fd2bd56..9bb308a 100644
> --- a/Documentation/devicetree/bindings/gpio/led.txt
> +++ b/Documentation/devicetree/bindings/gpio/led.txt
> @@ -55,4 +55,4 @@ run-control {
>  		gpios = <&mpc8572 7 0>;
>  		default-state = "on";
>  	};
> -}
> +};

Looks good to me?

More a Grant question, really. (And probably something for his tree.)

Rob
-- 
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation.  Pick one.

  reply	other threads:[~2012-06-24  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 18:41 [PATCH] LED: Fix missing semicolon in OF documentation Marek Vasut
2012-06-24  6:49 ` Rob Landley [this message]
2012-07-05 16:08 ` Rob Herring

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=4FE6B888.1090700@landley.net \
    --to=rob@landley.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-doc@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=rob.herring@calxeda.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 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.