From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] tegra: Use engineering names in DT compatible properties
Date: Tue, 5 Jul 2011 23:55:39 -0600 [thread overview]
Message-ID: <20110706055539.GG9978@ponder.secretlab.ca> (raw)
In-Reply-To: <1309897762-23564-1-git-send-email-swarren@nvidia.com>
On Tue, Jul 05, 2011 at 02:29:19PM -0600, Stephen Warren wrote:
> Grant, these 3 patches are for the devicetree/test branch. I kept them
> separated in the hope they'll squash into existing patches already there.
Thanks, I'll pick them up and squash them in.
g.
>
> Stephen Warren (3):
> mmc/tegra: Use engineering names in DT compatible property
> ARM: tegra: Use engineering names in DT compatible property
> dt: docs: tegra: Use engineering names in DT compatible property
>
> Documentation/devicetree/usage-model | 12 ++--
> arch/arm/boot/dts/tegra-harmony.dts | 4 +-
> arch/arm/boot/dts/tegra-seaboard.dts | 4 +-
> arch/arm/boot/dts/tegra20.dtsi | 162 ++++++++++++++++++++++++++++++++++
> arch/arm/boot/dts/tegra250.dtsi | 162 ----------------------------------
> arch/arm/mach-tegra/board-dt.c | 32 ++++----
> drivers/mmc/host/sdhci-pltfm.c | 2 +-
> 7 files changed, 189 insertions(+), 189 deletions(-)
> create mode 100644 arch/arm/boot/dts/tegra20.dtsi
> delete mode 100644 arch/arm/boot/dts/tegra250.dtsi
>
prev parent reply other threads:[~2011-07-06 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 20:29 [PATCH 0/3] tegra: Use engineering names in DT compatible properties Stephen Warren
2011-07-05 20:29 ` [PATCH 1/3] mmc/tegra: Use engineering names in DT compatible property Stephen Warren
2011-07-05 20:29 ` [PATCH 2/3] ARM: tegra: " Stephen Warren
2011-07-05 20:29 ` [PATCH 3/3] dt: docs: " Stephen Warren
2011-07-06 5:55 ` 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=20110706055539.GG9978@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).