All of lore.kernel.org
 help / color / mirror / Atom feed
From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: vexpress issues in next-20121029
Date: Thu, 08 Nov 2012 18:54:54 +0000	[thread overview]
Message-ID: <1352400894.20549.33.camel@hornet> (raw)
In-Reply-To: <509AC63C.1070309@wwwdotorg.org>

On Wed, 2012-11-07 at 20:36 +0000, Stephen Warren wrote:
> On 10/29/2012 02:24 PM, Stephen Warren wrote:
> > 2) With those calls commented out, I find that
> > vexpress_sysreg_init_leds() is device_initcall, and so executes even
> > when not running on vexpress HW. This crashes on Tegra (which I have
> > converted to single-zImage locally).
> 
> This issue still appears to be present in next-20121107.

Yes, sorry about that - last week I've posted patches adding a generic
memory mapped leds driver and using it instead, but haven't managed to
get any comments from the maintainers. I've pinged them today and if I
hear nothing till tomorrow, I'll remove the offending code from
vexpress-sysreg.c completely and wait will this stuff till next cycle.

Pawe?

      reply	other threads:[~2012-11-08 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29 20:24 vexpress issues in next-20121029 Stephen Warren
2012-10-30 16:16 ` Pawel Moll
2012-11-05  9:35   ` Russell King - ARM Linux
2012-11-05  9:45     ` Russell King - ARM Linux
2012-11-05 14:43       ` Pawel Moll
2012-11-05 16:47         ` Arnd Bergmann
2012-11-05 17:19           ` Pawel Moll
2012-11-05 17:52             ` Arnd Bergmann
2012-11-05 18:12               ` Pawel Moll
2012-11-07 20:36 ` Stephen Warren
2012-11-08 18:54   ` Pawel Moll [this message]

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=1352400894.20549.33.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.