[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1803142035520.1946@nanos.tec.linutronix.de>
Date: Wed, 14 Mar 2018 20:36:25 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Palmer Dabbelt <palmer@...ive.com>
cc: linux@...linux.org.uk, catalin.marinas@....com,
Will Deacon <will.deacon@....com>, jonas@...thpole.se,
stefan.kristiansson@...nalahti.fi, shorne@...il.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
openrisc@...ts.librecores.org, linux-riscv@...ts.infradead.org
Subject: Re: [PATCH v3 3/5] arm: Convert to GENERIC_IRQ_MULTI_HANDLER
On Wed, 14 Mar 2018, Palmer Dabbelt wrote:
> On Wed, 14 Mar 2018 10:07:35 PDT (-0700), tglx@...utronix.de wrote:
> > On Wed, 7 Mar 2018, Palmer Dabbelt wrote:
> >
> > > This converts the ARM port to use the recently added
> > > GENERIC_IRQ_MULTI_HANDLER, which is essentially just a copy of ARM's
> > > existhing MULTI_IRQ_HANDLER. The only changes are:
> > >
> > > * handle_arch_irq is now defined in a generic C file instead of an
> > > arm-specific assembly file.
> > > * handle_arch_irq is not marked as __ro_after_init.
> >
> > Why? What prevents the generic implementation from doing so?
>
> Sorry, I guess that should have said "handle_arch_irq was not marked as
> __ro_after_init". The patch set has __ro_after_init for the generic
> implementation, which was not the case for the arm version.
That makes sense.... I'll fix that up.
Thanks,
tglx
Powered by blists - more mailing lists