[PATCH 0/3] GPMC NAND isr using standard API

[Ivan Djelic]

On Tue, May 15, 2012 at 03:38:09PM +0100, Afzal Mohammed wrote:
> Hi Tony, Artem,
> 
> This series creates a fictitious GPMC interrupt chip and provide the
> clients with interrupts that could be handled using standard APIs.
> This helps in removing the requirement of driver of peripheral
> connected to GPMC having the knowledge about GPMC. The only user is
> OMAP NAND driver, it has also been modified to use interrupts provided
> by imaginary GPMC chip.
> 
> This series has a dependency on [2], while [2] has a trivial
> dependency on [1].
> 
> With this series plus [1,2], GPMC driver conversion which is going to
> happen shortly will not create noticable effect outside of
> arch/arm/*omap*/.
> 
> If this series along with [1,2] can be taken in for 3.5, ripples felt
> by MTD drivers upon GPMC driver conversion would be minimal.

Hi Afzal,

I tried to take your series of patches, but I had issues with the
first [1] (I did not try the others): it depends on the following patch,
which is not in the l2-mtd-2.6 tree:

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg68258.html

and it does not apply anyway to l2-mtd-2.6 because of (at least) the
following patches:

http://lists.infradead.org/pipermail/linux-mtd/2012-April/040631.html
http://lists.infradead.org/pipermail/linux-mtd/2012-April/040724.html

So, do you think you could rebase your series on l2-mtd-2.6 ?
And maybe merge the 3 series into a single one, if they have circular
dependencies ?

Thanks,

--
Ivan

[1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg68581.html
[2] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg68652.html