From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings
Date: Fri, 12 Jul 2013 11:37:20 +0200 [thread overview]
Message-ID: <20130712093720.GE24370@lukather> (raw)
In-Reply-To: <20130705101946.GA5584@e102568-lin.cambridge.arm.com>
Hi Lorenzo,
On Fri, Jul 05, 2013 at 11:19:46AM +0100, Lorenzo Pieralisi wrote:
> On Sun, Jun 30, 2013 at 10:48:46AM +0100, Lorenzo Pieralisi wrote:
> > On Sat, Jun 29, 2013 at 08:38:19PM +0100, Russell King - ARM Linux wrote:
> > > On Fri, Jun 28, 2013 at 01:05:42PM -0700, Olof Johansson wrote:
> > > > On Fri, Jun 28, 2013 at 1:03 PM, Maxime Ripard
> > > > <maxime.ripard@free-electrons.com> wrote:
> > > > > On Fri, Jun 28, 2013 at 06:15:32PM +0100, Lorenzo Pieralisi wrote:
> > > > >> The patch above should already be queued in next/dt right ?
> > > > >
> > > > > Indeed.
> > > > >
> > > > > Then why the latest patch of your patchset got in 3.10, while the
> > > > > patches actually fixing the DT it would have impacted were delayed to
> > > > > 3.11?
> > > > >
> > > > > (And why was it merged so late in the development cycle?)
> > > >
> > > > This. So now we have to scramble because some device trees will
> > > > produce warnings at boot.
> > > >
> > > > Russell, the alternative is to revert Lorenzo's patch for 3.10 (and
> > > > re-introduce it for 3.11). Do you have a preference?
> > >
> > > Sorry but I really don't understand what all the fuss in this thread
> > > is about.
> > >
> > > This thread seems to be saying that two development patches were
> > > merged, which were 7762/1 and 7763/1, and that 7764/1 is a fix?
> > > Are you sure about that, because that's not how they're described,
> > > and not how they look either.
> >
> > As Olof's warning downgrade is being merged (thanks for that and apologies for
> > failing to explain patches dependencies properly and stable related issues),
> > 7764/1 won't apply cleanly anymore. Can you please drop it from the patch
> > system, I will update it and test it first thing tomorrow and send a
> > final version to the patch system.
>
> Patch 7779/1, replacing 7764/1 is in the patch system now, and is ready
> to get merged.
>
> Unfortunately cpu/cpus bindings documentation updates, following:
>
> https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-June/036735.html
> https://lists.ozlabs.org/pipermail/devicetree-discuss/2013-May/033779.html
>
> were not pulled in the kernel. This is an issue since this means that
> we still have no reference in the kernel or wherever it has to be, to
> the final cpus/cpu bindings for ARM and ARM64 provided in the pull
> request link above (that has been reviewed to death and acknowledged).
>
> It is a significant overhaul of cpu/cpus bindings standard for ARM/ARM64,
> covering all CPUs harking back to arm926 and beyond, and should be final.
>
> dts updates following that standard have already been pulled into 3.11
> through arm-soc.
>
> IMHO the bindings contained in pull request above must be merged in the
> kernel asap, I would like to ask you please what should I do to get them in
> please. If we want to move bindings documentation elsewhere let's do it,
> as long as there is a published standard I am happy and will stop annoying
> you with this stuff.
Just to be clear, I had no problems with the patches themselves, but
just the way it was merged.
That being said, I think every DTS patch you did should be merged by
now, only the second patch of this serie for the A10S hasn't.
Arnd, Olof, could you just apply the patch 2 for a 3.11-rc*? It's the
only rc patch for the sunxi platform for now, so I don't think a pull
request would be worth it, but I can send one anyway if you prefer.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130712/cb1d3c36/attachment.sig>
next prev parent reply other threads:[~2013-07-12 9:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:44 [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings Maxime Ripard
2013-06-28 16:44 ` [PATCH 1/2] ARM: dts: sunxi: cpus/cpu nodes dts updates Maxime Ripard
2013-06-28 16:44 ` [PATCH 2/2] sunxi: a10s: dtsi: Convert cpu node to the new cpu bindings Maxime Ripard
2013-06-28 17:15 ` [PATCH 0/2] ARM: sunxi: Convert DTSI to new CPU bindings Lorenzo Pieralisi
2013-06-28 20:03 ` Maxime Ripard
2013-06-28 20:05 ` Olof Johansson
2013-06-28 21:45 ` Lorenzo Pieralisi
2013-06-29 18:07 ` Maxime Ripard
2013-06-29 19:03 ` Lorenzo Pieralisi
2013-06-29 19:38 ` Russell King - ARM Linux
2013-06-29 20:11 ` Lorenzo Pieralisi
2013-06-29 22:54 ` Olof Johansson
2013-06-29 23:14 ` Russell King - ARM Linux
2013-06-29 23:20 ` Olof Johansson
2013-06-30 9:48 ` Lorenzo Pieralisi
2013-07-05 10:19 ` Lorenzo Pieralisi
2013-07-12 9:37 ` Maxime Ripard [this message]
2013-07-02 12:12 ` Nicolas Ferre
2013-07-02 12:56 ` 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=20130712093720.GE24370@lukather \
--to=maxime.ripard@free-electrons.com \
--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).