[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1009272152360.2416@localhost6.localdomain6>
Date: Mon, 27 Sep 2010 21:54:06 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: richard -rw- weinberger <richard.weinberger@...il.com>
cc: LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
linux-alpha@...r.kernel.org, linux-cris-kernel@...s.com,
Haavard Skinnemoen <hskinnemoen@...el.com>,
Tony Luck <tony.luck@...el.com>, linux-ia64@...r.kernel.org,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Hirokazu Takata <takata@...ux-m32r.org>,
Greg Ungerer <gerg@...inux.org>, Jeff Dike <jdike@...toit.com>,
linux-parisc@...r.kernel.org, Chris Zankel <chris@...kel.net>,
linux-arch@...r.kernel.org
Subject: Re: [RFC trollpatch 1/1] genirq: Remove the fits all and nothing
__do_IRQ() code
On Mon, 27 Sep 2010, richard -rw- weinberger wrote:
> On Wed, Sep 8, 2010 at 8:14 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
> > __do_IRQ() has been deprecated after a two years migration phase in
> > The following architectures are still using __do_IRQ():
> >
> > alpha, cris, ia64, h8300, m32r, m68knommu, parisc, um
> >
>
> Maybe I'm naive but shouldn't this path work?
> Does um need some extra work?
Yes. It needs to set the proper flow handlers. Look for set_irq_chip*
functions and how they are used in other archs.
Thanks,
tglx
Powered by blists - more mailing lists