From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 REPOST 1/9] Validate dtc is new enough
Date: Fri, 02 Aug 2013 16:23:37 -0600 [thread overview]
Message-ID: <51FC3169.4040506@wwwdotorg.org> (raw)
In-Reply-To: <1374685764-4828-2-git-send-email-swarren@wwwdotorg.org>
On 07/24/2013 11:09 AM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Subsequent patches assume that dtc supports various recent features.
> These are available in dtc 1.4.0. Validate that dtc is at least that
> version.
Tom, do these patches look good?
next prev parent reply other threads:[~2013-08-02 22:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 17:09 [U-Boot] [PATCH V2 REPOST 0/9] rely on latest dtc, simplify Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 1/9] Validate dtc is new enough Stephen Warren
2013-08-02 22:23 ` Stephen Warren [this message]
2013-08-03 0:32 ` Tom Rini
2013-08-03 14:11 ` Albert ARIBAUD
2013-08-03 15:31 ` Tom Rini
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 2/9] xilinx: move microblaze-generic .dts to standard location Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 3/9] dts/Makefile: simplify dtc invocation Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 4/9] dts/Makefile: unify cpp/dtc include paths Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 5/9] dt: don't use ARCH_CPU_DTS Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 6/9] dts/Makefile: don't define ARCH_CPU_DTS, BOARD_DTS Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 7/9] config: don't define CONFIG_ARCH_DEVICE_TREE Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 8/9] dts/Makefile: don't use cpp -P Stephen Warren
2013-07-24 17:09 ` [U-Boot] [PATCH V2 REPOST 9/9] dts/Makefile: pass -undef -D__DTS__ to cpp Stephen Warren
2013-08-03 19:30 ` [U-Boot] [PATCH V2 REPOST 0/9] rely on latest dtc, simplify Tom Rini
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=51FC3169.4040506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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