From: Tony Lindgren <tony@atomide.com>
To: Olof Johansson <olof@lixom.net>
Cc: "arm@kernel.org" <arm@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] omap fixes against v3.13-rc1
Date: Tue, 26 Nov 2013 19:52:17 -0800 [thread overview]
Message-ID: <20131127035216.GW26766@atomide.com> (raw)
In-Reply-To: <CAOesGMh8hq5UbL5ion=fgAecfkMLw3E5+2m8T2LbdqgYafFK8Q@mail.gmail.com>
* Olof Johansson <olof@lixom.net> [131126 19:34]:
> On Tue, Nov 26, 2013 at 5:30 PM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > As we're moving omap2+ to be device tree only for v3.14, I'd like to
> > have v3.13 work equally well for legacy based booting and device tree
> > based booting. So there will be likely few more device tree related
> > booting patches trickling in.
>
> Pulled, thanks. Do you have a feel for how much more of DT-vs-legacy
> patches you expect for 3.13? I'm not saying no to them at this point
> but it'd be good to know roughly what to expect.
Thanks, I currently only have four more coming but these still need
testing and acks:
net: smc91x: Fix device tree based configuration so it's usable
of/platform: Fix no irq domain found errors when populating interrupts
ARM: dts: Fix omap serial wake-up when booted with device tree
ARM: OMAP2+: Fix overwriting hwmod data with data from device tree
Then there will probably be few patches from other people but the
four above are currently the only ones that I'm aware of that can be
show stoppers for booting omaps (and also other SoCs) with device tree.
Regards,
Tony
next prev parent reply other threads:[~2013-11-27 3:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52954b58.8659420a.7af3.ffffeeabSMTPIN_ADDED_BROKEN@mx.google.com>
2013-11-27 3:33 ` [GIT PULL] omap fixes against v3.13-rc1 Olof Johansson
2013-11-27 3:52 ` Tony Lindgren [this message]
2013-11-27 1:30 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2013-11-27 1:30 Tony Lindgren
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=20131127035216.GW26766@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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).