Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: TI-Davinci 6446 oops on interrupts
Date: Mon, 6 Jun 2011 23:31:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1106062330380.13964@ionos> (raw)
In-Reply-To: <4DECF32B.6000508@selfish.org>

Kevin,

On Mon, 6 Jun 2011, Holger Freyther wrote:

> On 06/06/2011 05:25 PM, Thomas Gleixner wrote:
> 
> > Crap, yes. The code which does the chained handler setup overwrites
> > chip_data.
> > 
> 
> Ah, you were too fast in the end, I just finished reading linux/irq.h. :)
> 
> 
> 
> > Subject: arm: davinci: Fix fallout from generic irq chip conversion
> > From: Thomas Gleixner <tglx@linutronix.de>
> > Date: Mon, 06 Jun 2011 11:51:43 +0200
> > 
> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> 
> Tested-by: Holger Hans Peter Freyther <holger@freyther.de>

can you please pick that up? It should have a Cc: stable at kernel.org
tag as well.

Thanks,

	tglx

  reply	other threads:[~2011-06-06 21:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 12:41 TI-Davinci 6446 oops on interrupts Holger Freyther
2011-06-06 13:40 ` Holger Hans Peter Freyther
2011-06-06 14:54   ` Thomas Gleixner
2011-06-06 15:10     ` Holger Freyther
2011-06-06 15:25       ` Thomas Gleixner
2011-06-06 15:32         ` Holger Freyther
2011-06-06 21:31           ` Thomas Gleixner [this message]
2011-06-06 22:50             ` Kevin Hilman
2011-06-07 18:13             ` Nori, Sekhar
2011-06-07 22:59               ` Thomas Gleixner
2011-06-10 18:47         ` Holger Freyther
2011-06-06 14:49 ` Thomas Gleixner
2011-06-06 16:32   ` Russell King - ARM Linux
2011-06-06 17:45     ` Holger Freyther
2011-06-06 17:50       ` Thomas Gleixner
2011-06-06 21:30     ` Thomas Gleixner
2011-06-06 16:30 ` Russell King - ARM Linux

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=alpine.LFD.2.02.1106062330380.13964@ionos \
    --to=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox