linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: Harmony: Use engineering names in DT compatible property
Date: Tue, 5 Jul 2011 23:50:18 -0600	[thread overview]
Message-ID: <20110706055018.GF9978@ponder.secretlab.ca> (raw)
In-Reply-To: <1309897408-23085-1-git-send-email-swarren@nvidia.com>

On Tue, Jul 05, 2011 at 02:23:28PM -0600, Stephen Warren wrote:
> Engineering names are more stable than marketing names. Hence, use them
> for Device Tree compatible properties instead.
> 
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> Grant, this is against devicetree/arm, and only makes sense there; I'll
> send a separate patch for the equivalent change in devicetree/test, since
> the file is radically different there.

devicetree/arm actually does track devicetree/test, just a subset of
the patches in it (although it isn't obvious since I use stgit to make
devicetree/arm a stable branch that never rebases.

I'll make sure both devicetree/arm and devicetree/test are fixed up.

g.

> 
>  arch/arm/boot/dts/tegra-harmony.dts |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/tegra-harmony.dts b/arch/arm/boot/dts/tegra-harmony.dts
> index 81032e7..4ad8ade 100644
> --- a/arch/arm/boot/dts/tegra-harmony.dts
> +++ b/arch/arm/boot/dts/tegra-harmony.dts
> @@ -3,5 +3,5 @@
>  
>  / {
>  	model = "NVIDIA Tegra2 Harmony evaluation board";
> -	compatible = "nvidia,harmony", "nvidia,tegra250";
> +	compatible = "nvidia,harmony", "nvidia,tegra20";
>  };
> -- 
> 1.7.0.4
> 

      reply	other threads:[~2011-07-06  5:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 20:23 [PATCH] ARM: tegra: Harmony: Use engineering names in DT compatible property Stephen Warren
2011-07-06  5:50 ` 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=20110706055018.GF9978@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.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).