From: Sebastian Reichel <sre@ring0.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: Add missing reg, interrupt and dma entries for omap3
Date: Mon, 11 Nov 2013 18:48:40 +0100 [thread overview]
Message-ID: <20131111174839.GA15331@earth.universe> (raw)
In-Reply-To: <20131111165638.GP15154@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Mon, Nov 11, 2013 at 08:56:39AM -0800, Tony Lindgren wrote:
> * Sebastian Reichel <sre@ring0.de> [131110 15:48]:
> > Hi Tony,
> >
> > On Thu, Oct 17, 2013 at 03:15:22PM -0700, Tony Lindgren wrote:
> > > Looks like omap3 is still relying on hwmod data for some basic
> > > device tree information. Let's add the information to omap3.dtsi
> > > so we can remove the related hwmod data once omap3 is DT only.
> >
> > This patch fixes a regression in omap3 DT boot introduced by
> > commit 2a0b965cfb6efc667228831fc3a30308b4f94a87. This commit
> > assumes, that interrupts are specified via DT data if booted
> > via DT.
>
> Yes sorry about that, this should have been merged as a fix
> earlier to avoid breaking things during the merge window.
> Looks like I only tested 2a0b965cfb6efc667228831fc3a30308b4f94a87
> separately on omap4 or something and forgot about the dependency.
No problem, but I think its currently not queued for 3.13.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-11 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 22:15 [PATCH] ARM: dts: Add missing reg, interrupt and dma entries for omap3 Tony Lindgren
2013-10-18 15:55 ` Benoit Cousson
2013-11-10 23:47 ` Sebastian Reichel
2013-11-11 16:56 ` Tony Lindgren
2013-11-11 17:48 ` Sebastian Reichel [this message]
2013-11-11 18:16 ` 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=20131111174839.GA15331@earth.universe \
--to=sre@ring0.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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).