From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Florian Vaussard <florian.vaussard@epfl.ch>,
Tony Lindgren <tony@atomide.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/5] ARM: dts: OMAP2+: use preprocessor for device trees
Date: Tue, 28 May 2013 10:41:20 +0200 [thread overview]
Message-ID: <51A46DB0.5020508@epfl.ch> (raw)
In-Reply-To: <1369666354-29152-1-git-send-email-florian.vaussard@epfl.ch>
On 05/27/2013 04:52 PM, Florian Vaussard wrote:
> Hello,
>
> Following a similar proposal by Stephen Warren for tegra [1], this series
> makes use of the C preprocessor when compiling OMAP DT files, and
> accomplishes some improvements to improve overall readability.
>
I realized that I should also address am* devices. I will wait for comments
on this version, then post a v4. Sorry for the noise.
Regards,
Florian
next prev parent reply other threads:[~2013-05-28 8:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 14:52 [PATCH v3 0/5] ARM: dts: OMAP2+: use preprocessor for device trees Florian Vaussard
2013-05-27 14:52 ` [PATCH v3 1/5] ARM: dts: OMAP2+: use #include for all " Florian Vaussard
2013-05-27 14:52 ` [PATCH v3 2/5] ARM: dts: OMAP2+: use existing constants for GPIOs Florian Vaussard
2013-05-27 14:52 ` [PATCH v3 3/5] ARM: dts: OMAP4/5: use existing constants for IRQs Florian Vaussard
2013-05-27 14:52 ` [PATCH v3 4/5] ARM: dts: OMAP2+: header file for pinctrl constants Florian Vaussard
2013-05-27 14:52 ` [PATCH v3 5/5] ARM: dts: OMAP2+: use " Florian Vaussard
2013-05-28 8:41 ` Florian Vaussard [this message]
2013-05-29 8:46 ` [PATCH v3 0/5] ARM: dts: OMAP2+: use preprocessor for device trees Benoit Cousson
2013-05-29 8:53 ` Florian Vaussard
2013-05-29 9:04 ` Benoit Cousson
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=51A46DB0.5020508@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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).