From: Lorenzo Pieralisi <lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>
To: "grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org"
<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [GIT PULL] ARM DT cpus/cpu bindings documentation updates
Date: Wed, 26 Jun 2013 10:55:04 +0100 [thread overview]
Message-ID: <20130626095504.GC22333@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20130523103315.GA2866-7AyDDHkRsp3ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
Hi Grant, Rob,
On Thu, May 23, 2013 at 11:33:15AM +0100, Lorenzo Pieralisi wrote:
> Hi Grant, Rob,
>
> please pull the cpus/cpu nodes bindings updates for ARM. This pull
> request completes my previous pull request:
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-May/169110.html
Please let me know if you have any objection to these two pull requests
(the one I am replying to and the one provided in the link above). I
sent them quite early so I am just reminding you lest you missed them.
These bindings are quite important and without them all in-kernel dts files,
cpu map parsing code and topology updates are meaningless, I really hope you
can queue them for this upcoming merge window.
They are based against early kernel versions (3.10-rc1 and 3.10-rc2), but
they fast-forward cleanly to -rc7, please let me know if you want me to
send pull requests with branches updated to -rc7, I do not think it is
necessary.
Thank you very much indeed,
Lorenzo
>
> with the required changes for cpus/cpu nodes.
>
> Thanks a lot,
> Lorenzo
>
> The following changes since commit c7788792a5e7b0d5d7f96d0766b4cb6112d47d75:
>
> Linux 3.10-rc2 (2013-05-20 14:37:38 -0700)
>
> are available in the git repository at:
>
> git://linux-arm.org/linux-2.6-lp.git dt-cpus-bindings
>
> for you to fetch changes up to 8e11f862d6a5491bb5f8ef73e13cfd66562e7be3:
>
> Documentation: devicetree: arm: cpus/cpu nodes bindings updates (2013-05-23 10:46:46 +0100)
>
> ----------------------------------------------------------------
> Lorenzo Pieralisi (1):
> Documentation: devicetree: arm: cpus/cpu nodes bindings updates
>
> Documentation/devicetree/bindings/arm/cpus.txt | 459 ++++++++++++++++++++++---
> 1 file changed, 412 insertions(+), 47 deletions(-)
>
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss
>
prev parent reply other threads:[~2013-06-26 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 10:33 [GIT PULL] ARM DT cpus/cpu bindings documentation updates Lorenzo Pieralisi
[not found] ` <20130523103315.GA2866-7AyDDHkRsp3ZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2013-06-26 9:55 ` Lorenzo Pieralisi [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=20130626095504.GC22333@e102568-lin.cambridge.arm.com \
--to=lorenzo.pieralisi-5wv7dgnigg8@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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).