From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] Urgent omap4 legacy interrupt regression fix for v3.19-rc series
Date: Mon, 19 Jan 2015 16:23:56 -0800 [thread overview]
Message-ID: <20150120002356.GJ16883@quad.lixom.net> (raw)
In-Reply-To: <20150119230950.GA7718@atomide.com>
On Mon, Jan 19, 2015 at 03:09:51PM -0800, Tony Lindgren wrote:
> The following changes since commit 7ac72746aa9bb305fa74b44ec73eae99bbbe9b66:
>
> ARM: dts: Revert disabling of smc91x for n900 (2015-01-06 08:49:57 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.19/gic-regression-v2
>
> for you to fetch changes up to 0fb22a8fb7f3bc1b00a36d4a97ce4f93191f7559:
>
> ARM: OMAP: Work around hardcoded interrupts (2015-01-17 08:56:12 -0800)
>
> ----------------------------------------------------------------
> A rather urgent pull request to fix omap4 legacy interrupts.
>
> The legacy interrupts on omap4 got broken when gic got changed to
> use irq_domain_add_linear() instead of the irq_domain_add_legacy(). We
> still have the hardcoded legacy IRQ numbers in use in several places,
> most notably the in the legacy DMA. It took a while to figure out
> what the problem was and how it should be fixed for the -rc series.
>
> Also include is a regression fix for the dra7 dwc3 suspend.
>
Merged.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Urgent omap4 legacy interrupt regression fix for v3.19-rc series
Date: Mon, 19 Jan 2015 16:23:56 -0800 [thread overview]
Message-ID: <20150120002356.GJ16883@quad.lixom.net> (raw)
In-Reply-To: <20150119230950.GA7718@atomide.com>
On Mon, Jan 19, 2015 at 03:09:51PM -0800, Tony Lindgren wrote:
> The following changes since commit 7ac72746aa9bb305fa74b44ec73eae99bbbe9b66:
>
> ARM: dts: Revert disabling of smc91x for n900 (2015-01-06 08:49:57 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v3.19/gic-regression-v2
>
> for you to fetch changes up to 0fb22a8fb7f3bc1b00a36d4a97ce4f93191f7559:
>
> ARM: OMAP: Work around hardcoded interrupts (2015-01-17 08:56:12 -0800)
>
> ----------------------------------------------------------------
> A rather urgent pull request to fix omap4 legacy interrupts.
>
> The legacy interrupts on omap4 got broken when gic got changed to
> use irq_domain_add_linear() instead of the irq_domain_add_legacy(). We
> still have the hardcoded legacy IRQ numbers in use in several places,
> most notably the in the legacy DMA. It took a while to figure out
> what the problem was and how it should be fixed for the -rc series.
>
> Also include is a regression fix for the dra7 dwc3 suspend.
>
Merged.
-Olof
next prev parent reply other threads:[~2015-01-20 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 23:09 [GIT PULL] Urgent omap4 legacy interrupt regression fix for v3.19-rc series Tony Lindgren
2015-01-19 23:09 ` Tony Lindgren
2015-01-20 0:23 ` Olof Johansson [this message]
2015-01-20 0:23 ` Olof Johansson
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=20150120002356.GJ16883@quad.lixom.net \
--to=olof@lixom.net \
--cc=arm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.