From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
stable@vger.kernel.org, arm@kernel.org
Subject: Re: REGRESSION: omap3 fails to boot
Date: Sat, 10 Mar 2012 19:20:22 +0000 [thread overview]
Message-ID: <20120310192022.GB22875@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAK=WgbaAaUNr8uFU1bTcOMS1nbi_uN=Mw0=mm5rsQv2at8TUpg@mail.gmail.com>
On Sat, Mar 10, 2012 at 08:31:50PM +0200, Ohad Ben-Cohen wrote:
> On Sat, Mar 10, 2012 at 8:08 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > Seems to be that the OMAP mailbox stuff is buggered:
>
> Can you please recheck with the following commit (already in mainline):
>
> commit 134d12fae0bb8f3d60dc7440a9e1950bb5427167
> Author: Ohad Ben-Cohen <ohad@wizery.com>
> Date: Sun Mar 4 12:01:11 2012 +0200
>
> ARM: OMAP: fix iommu, not mailbox
>
> For some weird (freudian?) reason, commit 435792d "ARM: OMAP: make
> iommu subsys_initcall to fix builtin omap3isp" unintentionally changed
> the mailbox's initcall instead of the iommu's.
>
> Fix that.
>
> Reported-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
> Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: Joerg Roedel <Joerg.Roedel@amd.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Why isn't this copied to the stable folk? The commit which breaks this
was copied there, so that's going to break stable kernels.
next prev parent reply other threads:[~2012-03-10 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:08 REGRESSION: omap3 fails to boot Russell King - ARM Linux
2012-03-10 18:31 ` Ohad Ben-Cohen
2012-03-10 19:20 ` Russell King - ARM Linux [this message]
2012-03-10 19:37 ` Ohad Ben-Cohen
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=20120310192022.GB22875@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arm@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=stable@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