From: Randy Dunlap <rdunlap@infradead.org>
To: Samarth Parikh <samarthp@ymail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] Documentation: added missing semicolon in at25 dts example
Date: Tue, 15 Jul 2014 08:36:47 -0700 [thread overview]
Message-ID: <53C54A8F.8080909@infradead.org> (raw)
In-Reply-To: <1405430449-21283-1-git-send-email-samarthp@ymail.com>
[adding dt bindings people + list]
On 07/15/14 06:20, Samarth Parikh wrote:
> Added a missing semicolon ";" in device tree structure
> example of "EEPROMs (SPI) compatible with Atmel at25" in
> documentation of device tree bindings.
>
> Signed-off-by: Samarth Parikh <samarthp@ymail.com>
> ---
> Documentation/devicetree/bindings/misc/at25.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/misc/at25.txt b/Documentation/devicetree/bindings/misc/at25.txt
> index 1d34471..cf830bd 100644
> --- a/Documentation/devicetree/bindings/misc/at25.txt
> +++ b/Documentation/devicetree/bindings/misc/at25.txt
> @@ -24,7 +24,7 @@ Additional compatible properties are also allowed.
> Example:
> at25@0 {
> compatible = "atmel,at25", "st,m95256";
> - reg = <0>
> + reg = <0>;
> spi-max-frequency = <5000000>;
> spi-cpha;
> spi-cpol;
>
--
~Randy
next parent reply other threads:[~2014-07-15 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1405430449-21283-1-git-send-email-samarthp@ymail.com>
2014-07-15 15:36 ` Randy Dunlap [this message]
2014-07-15 15:41 ` [PATCH] Documentation: added missing semicolon in at25 dts example Mark Rutland
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=53C54A8F.8080909@infradead.org \
--to=rdunlap@infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=samarthp@ymail.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).