[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <afb69b1f-0c6b-7109-9e1d-edc49adf40f2@ti.com>
Date: Fri, 15 Feb 2019 20:44:42 +0530
From: Sekhar Nori <nsekhar@...com>
To: Bartosz Golaszewski <brgl@...ev.pl>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Kevin Hilman <khilman@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Marc Zyngier <marc.zyngier@....com>,
David Lechner <david@...hnology.com>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH v4 00/37] ARM: davinci: modernize the irq support
Marc,
On 14/02/19 8:21 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bgolaszewski@...libre.com>
>
> This series ports the davinci platform to using SPARSE_IRQ, cleans up
> the irqchip drivers and moves them over to drivers/irqchip.
>
> The series can be logically split into five parts. The first patch
> preemptively fixes a problem in an input driver that would have caused
> problems later. Patches (2-9) aim at introducing support for SPARSE_IRQ.
> They contain a couple changes required for that functionality and do some
> cleanup at the end.
>
> Third part (10-22) makes the aintc driver suitable for drivers/irqchip
> and eventually moves it over there.
>
> Part 4 (23-36) does the same for the cp-intc driver.
>
> Last patch removes unnecessary code.
>
> The series has been tested on da850-lcdk (for cp-intc) and
> dm365-evm (for aintc).
Do you have any further comments? If no, I would like to apply for v5.1
with your ack.
Thanks,
Sekhar
Powered by blists - more mailing lists