Vinod Koul <vinod.koul@xxxxxxxxx> writes: >> Would it be possible that I take that through the pxa tree, even it stays in >> drivers/dmaengine ? I want that to land in the next cycle, and I'll take the >> fixes and maintainance anyway on my back. > Sorry about the delay, I should be able to get this done in next few days > and if all ggod then it should in next before eow. Ok, great, that works for me. Given the size of that patch, I'm expecting to release a v3/v4 after your comments. If not, you should be aware that I have a local patch on patch 3/5 in [1]. -- Robert [1] diff --git a/drivers/dma/pxa_dma.c b/drivers/dma/pxa_dma.c index 9f80d51..5295fb7 100644 --- a/drivers/dma/pxa_dma.c +++ b/drivers/dma/pxa_dma.c @@ -1293,7 +1293,7 @@ static int pxad_init_phys(struct platform_device *op, ret = devm_request_irq(&op->dev, irq, pxad_chan_handler, IRQF_SHARED, "pxa-dma", phy); - if ((nr_irq == 1) && (irq == 0)) + if ((nr_irq == 1) && (i == 0)) ret = devm_request_irq(&op->dev, irq0, pxad_int_handler, IRQF_SHARED, "pxa-dma", pdev); -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
