From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 13/13] ARM: DT: kernel: DT cpu node bindings update
Date: Thu, 02 May 2013 12:31:05 -0600 [thread overview]
Message-ID: <5182B0E9.3090006@wwwdotorg.org> (raw)
In-Reply-To: <1366644455-16550-14-git-send-email-lorenzo.pieralisi@arm.com>
On 04/22/2013 09:27 AM, Lorenzo Pieralisi wrote:
> In order to extend the current cpu nodes bindings to newer CPUs
> inclusive of AArch64 and to update support for older ARM CPUs this
> patch updates device tree documentation for the cpu nodes bindings.
Since I'm late reviewing this due to vacation, I imagine this has been
applied by now. But for the record, the structure of the DT binding
documentation in this version does look much better to me, and addresses
any concerns I had with v1.
next prev parent reply other threads:[~2013-05-02 18:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 15:27 [RFC PATCH v2 00/13] ARM: DT cpu bindings updates Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 01/13] ARM: DT: kernel: move temporary cpu map stack array to static data Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 02/13] ARM: mach-mv78xx0: cpus/cpu node dts updates Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 03/13] ARM: mach-at91: " Lorenzo Pieralisi
2013-04-22 15:48 ` Nicolas Ferre
2013-04-23 13:11 ` Rob Herring
2013-04-23 13:25 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-23 13:53 ` Lorenzo Pieralisi
2013-04-23 19:52 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-24 9:29 ` Lorenzo Pieralisi
2013-04-24 12:45 ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-22 15:27 ` [RFC PATCH v2 04/13] ARM: mach-exynos: cpus/cpu nodes " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 05/13] ARM: mach-imx: " Lorenzo Pieralisi
2013-04-23 7:34 ` Shawn Guo
2013-04-22 15:27 ` [RFC PATCH v2 06/13] ARM: mach-lpc32xx: " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 07/13] ARM: mach-omap2: " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 08/13] ARM: mach-picoxcell: " Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 09/13] ARM: mach-shmobile: " Lorenzo Pieralisi
2013-04-23 1:55 ` Simon Horman
2013-04-22 15:27 ` [RFC PATCH v2 10/13] ARM: mach-spear: " Lorenzo Pieralisi
2013-04-23 6:18 ` Viresh Kumar
2013-04-22 15:27 ` [RFC PATCH v2 11/13] ARM: mach-sunxi: " Lorenzo Pieralisi
2013-04-24 7:15 ` Maxime Ripard
2013-04-22 15:27 ` [RFC PATCH v2 12/13] ARM: mach-vt8500: " Lorenzo Pieralisi
2013-04-23 2:13 ` Tony Prisk
2013-04-23 2:20 ` Tony Prisk
2013-04-23 9:16 ` Lorenzo Pieralisi
2013-04-23 9:15 ` Lorenzo Pieralisi
2013-04-23 2:43 ` Tony Prisk
2013-04-23 9:26 ` Lorenzo Pieralisi
2013-04-22 15:27 ` [RFC PATCH v2 13/13] ARM: DT: kernel: DT cpu node bindings update Lorenzo Pieralisi
2013-04-23 2:46 ` Tony Prisk
2013-05-02 18:31 ` Stephen Warren [this message]
2013-05-03 9:15 ` Lorenzo Pieralisi
2013-04-22 16:41 ` [RFC PATCH v2 00/13] ARM: DT cpu bindings updates Will Deacon
2013-04-22 18:00 ` Lorenzo Pieralisi
2013-04-22 19:18 ` Arnd Bergmann
2013-04-23 9:09 ` Will Deacon
2013-04-23 9:34 ` Lorenzo Pieralisi
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=5182B0E9.3090006@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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).