devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Allen Martin <amartin@nvidia.com>,
	swarren@wwwdotorg.org, ldewangan@nvidia.com
Cc: devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] dt: fix tegra SPI binding examples
Date: Wed, 19 Dec 2012 12:33:48 +0000	[thread overview]
Message-ID: <20121219123348.19AFF3E0AD7@localhost> (raw)
In-Reply-To: <1355511912-23733-1-git-send-email-amartin@nvidia.com>

On Fri, 14 Dec 2012 11:05:12 -0800, Allen Martin <amartin@nvidia.com> wrote:
> Fix name of slink binding and address of sflash example to make it
> self consistent.
> 
> Change-Id: Ia89c3017c958bdf670036caf516eabce6f893096

Applied, thanks.

g.

> Signed-off-by: Allen Martin <amartin@nvidia.com>
> ---
>  Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt |    2 +-
>  Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt  |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt b/Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt
> index 8cf24f6..7b53da5 100644
> --- a/Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt
> +++ b/Documentation/devicetree/bindings/spi/nvidia,tegra20-sflash.txt
> @@ -13,7 +13,7 @@ Recommended properties:
>  
>  Example:
>  
> -spi@7000d600 {
> +spi@7000c380 {
>  	compatible = "nvidia,tegra20-sflash";
>  	reg = <0x7000c380 0x80>;
>  	interrupts = <0 39 0x04>;
> diff --git a/Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt b/Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt
> index f5b1ad1..eefe15e 100644
> --- a/Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt
> +++ b/Documentation/devicetree/bindings/spi/nvidia,tegra20-slink.txt
> @@ -13,7 +13,7 @@ Recommended properties:
>  
>  Example:
>  
> -slink@7000d600 {
> +spi@7000d600 {
>  	compatible = "nvidia,tegra20-slink";
>  	reg = <0x7000d600 0x200>;
>  	interrupts = <0 82 0x04>;
> -- 
> 1.7.10.4
> 
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss

-- 
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.

      reply	other threads:[~2012-12-19 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 19:05 [PATCH] dt: fix tegra SPI binding examples Allen Martin
2012-12-19 12:33 ` Grant Likely [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=20121219123348.19AFF3E0AD7@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=amartin@nvidia.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    /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).