Re: [patches] Re: [PATCH v2 4/4] RISC-V: Move to the new generic IRQ handler

2018-01-25 Thread Palmer Dabbelt
On Thu, 25 Jan 2018 00:31:53 PST (-0800), sho...@gmail.com wrote: On Wed, Jan 24, 2018 at 07:07:56PM -0800, Palmer Dabbelt wrote: The old mechanism for handling IRQs on RISC-V was pretty ugly: the arch code looked at the Kconfig entry for our first-level irqchip driver and called into it directl

Re: [PATCH v2 4/4] RISC-V: Move to the new generic IRQ handler

2018-01-25 Thread Stafford Horne
On Wed, Jan 24, 2018 at 07:07:56PM -0800, Palmer Dabbelt wrote: > The old mechanism for handling IRQs on RISC-V was pretty ugly: the arch > code looked at the Kconfig entry for our first-level irqchip driver and > called into it directly. > > This patch uses the new 0generic IRQ handling infastruc

Re: [PATCH v2 4/4] RISC-V: Move to the new generic IRQ handler

2018-01-24 Thread Christoph Hellwig
On Wed, Jan 24, 2018 at 07:07:56PM -0800, Palmer Dabbelt wrote: > The old mechanism for handling IRQs on RISC-V was pretty ugly: the arch > code looked at the Kconfig entry for our first-level irqchip driver and > called into it directly. > > This patch uses the new 0generic IRQ handling infastruc

[PATCH v2 4/4] RISC-V: Move to the new generic IRQ handler

2018-01-24 Thread Palmer Dabbelt
The old mechanism for handling IRQs on RISC-V was pretty ugly: the arch code looked at the Kconfig entry for our first-level irqchip driver and called into it directly. This patch uses the new 0generic IRQ handling infastructure, which essentially just deletes a bunch of code. This does add an ad