From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] DEBUG_LL platform updates for 3.2
Date: Fri, 21 Oct 2011 17:11:13 +0200 [thread overview]
Message-ID: <201110211711.13863.arnd@arndb.de> (raw)
In-Reply-To: <4EA18638.6020809@gmail.com>
On Friday 21 October 2011, Rob Herring wrote:
> On 10/21/2011 05:59 AM, Will Deacon wrote:
> > Hi Arnd,
> >
> > On Thu, Oct 20, 2011 at 03:57:49PM +0100, Arnd Bergmann wrote:
> >> Ok, thanks a lot. I've updated my branches now and recreated
> >> the for-next branch with these. Can you have a look to make sure
> >> that everything looks good there now?
> >
> > The cpu mapping and debug-ll stuff all looks good to me, thanks. On the
> > downside, I'm seeing a couple of problems with your for-next branch:
> >
> > 1. I can't compile if !CONFIG_OF, because l2x0_init isn't declared in
> > cache-l2x0.h. There seems to be some broken ifdeffery because of
> > what looks like duplicate commits d94527dd and 5260f15b, although
> > they are slightly different (and actually, both look broken to me
> > anyway!).
> >
>
> This was caught in linux-next.
It was my fault, but I think it works now.
> > 2. The GIC is hosed on versatile express. Reverting e3f14d3 ("ARM: gic: add
> > OF based initialization") and 2071a2a4 ("ARM: gic: add irq_domain support")
> > allows me to boot again.
> >
>
> I'll take a look at it today. Do you have more details or a boot log?
I hope you find this, otherwise I'll have to take the next/soc branch out of
for-next in the meantime to avoid the regressions.
Thanks for looking into it!
Arnd
next prev parent reply other threads:[~2011-10-21 15:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:38 [GIT PULL] DEBUG_LL platform updates for 3.2 Will Deacon
2011-10-03 8:35 ` Will Deacon
2011-10-07 20:51 ` Arnd Bergmann
2011-10-10 10:36 ` Will Deacon
2011-10-10 11:20 ` Arnd Bergmann
2011-10-10 13:32 ` Will Deacon
2011-10-11 7:52 ` Shawn Guo
2011-10-11 13:33 ` Arnd Bergmann
2011-10-11 15:09 ` Will Deacon
2011-10-11 18:48 ` Will Deacon
2011-10-11 19:25 ` Arnd Bergmann
2011-10-12 0:03 ` Nicolas Pitre
2011-10-12 8:30 ` Arnd Bergmann
2011-10-13 8:28 ` Russell King - ARM Linux
2011-10-13 13:39 ` Nicolas Pitre
2011-10-13 14:05 ` Russell King - ARM Linux
2011-10-13 18:36 ` Nicolas Pitre
2011-10-13 14:50 ` Arnd Bergmann
2011-10-13 23:09 ` Ryan Mallon
2011-10-13 23:40 ` Ryan Mallon
2011-10-14 2:32 ` Nicolas Pitre
2011-10-12 8:38 ` Jamie Iles
2011-10-12 20:16 ` Nicolas Pitre
2011-10-13 8:23 ` Russell King - ARM Linux
2011-10-13 18:46 ` Nicolas Pitre
2011-10-12 17:29 ` Russell King - ARM Linux
2011-10-12 17:35 ` Will Deacon
2011-10-12 18:01 ` Russell King - ARM Linux
2011-10-12 18:05 ` Will Deacon
2011-10-17 8:25 ` Russell King - ARM Linux
2011-10-17 9:23 ` Will Deacon
2011-10-20 14:57 ` Arnd Bergmann
2011-10-21 10:59 ` Will Deacon
2011-10-21 14:48 ` Rob Herring
2011-10-21 15:11 ` Arnd Bergmann [this message]
2011-10-21 15:15 ` Will Deacon
2011-10-21 18:03 ` Rob Herring
2011-10-21 23:04 ` Rob Herring
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=201110211711.13863.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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