From: Johan Hovold <jhovold@gmail.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [GIT PULL] ARM: OMAP: IRQ domain support for INTC
Date: Mon, 5 Mar 2012 14:58:38 +0100 [thread overview]
Message-ID: <20120305135838.GA2108@localhost> (raw)
In-Reply-To: <4F4E4F1D.7020109@ti.com>
On Wed, Feb 29, 2012 at 05:15:25PM +0100, Cousson, Benoit wrote:
> On 2/29/2012 12:48 AM, Tony Lindgren wrote:
> > * Cousson, Benoit<b-cousson@ti.com> [120227 08:04]:
> >> Hi Tony
> >>
> >> This series is based on the lo/dt + the irqdomain/next branch merged on top of it.
> >>
> >> Grant confirmed that the irqdomain/next is a stable branch and thus can be referenced for dependency.
> >>
> >> Please note that I will need that branch to base all the remaining OMAP DT stuff.
> >>
> >> Thanks,
> >> Benoit
> >>
> >>
> >> The following changes since commit 1f52299ec000e2161635b263d81ab92ea7f1f0a7:
> >> Benoit Cousson (1):
> >> Merge branch 'irqdomain/next' of git://git.secretlab.ca/git/linux-2.6 into for_3.4/dt_irq_domain2
> >>
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git for_3.4/dt_irq_domain
> >>
> >> Benoit Cousson (3):
> >> ARM: OMAP2/3: intc: Add DT support for TI interrupt controller
> >> arm/dts: OMAP3: Add interrupt-controller bindings for INTC
> >> ARM: OMAP2+: board-generic: Use of_irq_init API
> >>
> >> .../devicetree/bindings/arm/omap/intc.txt | 27 +++++++++
> >> arch/arm/boot/dts/omap3.dtsi | 6 +-
> >> arch/arm/mach-omap2/board-generic.c | 30 +++++-----
> >> arch/arm/mach-omap2/common.h | 12 ++++
> >> arch/arm/mach-omap2/irq.c | 60 ++++++++++++++++---
> >> 5 files changed, 109 insertions(+), 26 deletions(-)
> >> create mode 100644 Documentation/devicetree/bindings/arm/omap/intc.txt
> >
> > Hmm, looks like this now produces the following warning at least on omap3:
>
> Yes, Rajendra has just reported that issue with linux-next.
I'm getting the same warning and initialisation failure with 3.3-rc6 on
overo. Are these fixes queued up for 3.3 (and not just 3.4) somewhere?
Thanks,
Johan
next prev parent reply other threads:[~2012-03-05 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 16:36 [GIT PULL] ARM: OMAP: IRQ domain support for INTC Cousson, Benoit
2012-02-28 23:48 ` Tony Lindgren
2012-02-29 16:15 ` Cousson, Benoit
2012-02-29 21:42 ` Tony Lindgren
2012-03-05 13:58 ` Johan Hovold [this message]
2012-03-05 14:25 ` Cousson, Benoit
2012-03-05 15:03 ` Johan Hovold
2012-03-05 15:19 ` Cousson, Benoit
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=20120305135838.GA2108@localhost \
--to=jhovold@gmail.com \
--cc=b-cousson@ti.com \
--cc=grant.likely@secretlab.ca \
--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).