All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Daniel Mack <daniel@zonque.org>,
	Haojian Zhuang <haojian.zhuang@gmail.com>,
	dmaengine@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2 0/5] Driver for pxa architectures
Date: Sun, 03 May 2015 20:47:02 +0200	[thread overview]
Message-ID: <87vbg9v6qh.fsf@belgarion.home> (raw)
In-Reply-To: <20150503152300.GU3521@localhost> (Vinod Koul's message of "Sun, 3 May 2015 20:53:00 +0530")

Vinod Koul <vinod.koul@intel.com> 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);

WARNING: multiple messages have this Message-ID (diff)
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Driver for pxa architectures
Date: Sun, 03 May 2015 20:47:02 +0200	[thread overview]
Message-ID: <87vbg9v6qh.fsf@belgarion.home> (raw)
In-Reply-To: <20150503152300.GU3521@localhost> (Vinod Koul's message of "Sun, 3 May 2015 20:53:00 +0530")

Vinod Koul <vinod.koul@intel.com> 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);

  reply	other threads:[~2015-05-03 18:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-11 19:40 [PATCH v2 0/5] Driver for pxa architectures Robert Jarzmik
2015-04-11 19:40 ` Robert Jarzmik
2015-04-11 19:40 ` [PATCH v2 1/5] Documentation: dmaengine: pxa-dma design Robert Jarzmik
2015-04-11 19:40   ` Robert Jarzmik
2015-05-08  4:36   ` Vinod Koul
2015-05-08  4:36     ` Vinod Koul
2015-05-08 12:52     ` Robert Jarzmik
2015-05-08 12:52       ` Robert Jarzmik
2015-05-12 10:12       ` Vinod Koul
2015-05-12 10:12         ` Vinod Koul
2015-05-12 19:13         ` Robert Jarzmik
2015-05-12 19:13           ` Robert Jarzmik
2015-04-11 19:40 ` [PATCH v2 2/5] MAINTAINERS: add pxa dma driver to pxa architecture Robert Jarzmik
2015-04-11 19:40   ` Robert Jarzmik
2015-04-11 19:40 ` [PATCH v2 3/5] dmaengine: pxa: add pxa dmaengine driver Robert Jarzmik
2015-04-11 19:40   ` Robert Jarzmik
2015-05-08  6:34   ` Vinod Koul
2015-05-08  6:34     ` Vinod Koul
2015-05-08 12:28     ` Robert Jarzmik
2015-05-08 12:28       ` Robert Jarzmik
2015-05-09 11:59       ` Vinod Koul
2015-05-09 11:59         ` Vinod Koul
2015-05-09 17:00         ` Robert Jarzmik
2015-05-09 17:00           ` Robert Jarzmik
2015-04-11 19:40 ` [PATCH v2 4/5] dmaengine: pxa_dma: add debug information Robert Jarzmik
2015-04-11 19:40   ` Robert Jarzmik
2015-04-11 19:40 ` [PATCH v2 5/5] dmaengine: pxa_dma: add support for legacy transition Robert Jarzmik
2015-04-11 19:40   ` Robert Jarzmik
2015-04-19 20:01 ` [PATCH v2 0/5] Driver for pxa architectures Robert Jarzmik
2015-04-19 20:01   ` Robert Jarzmik
2015-04-26 19:59   ` Robert Jarzmik
2015-04-26 19:59     ` Robert Jarzmik
2015-05-01 20:13     ` Robert Jarzmik
2015-05-01 20:13       ` Robert Jarzmik
2015-05-03 15:23       ` Vinod Koul
2015-05-03 15:23         ` Vinod Koul
2015-05-03 18:47         ` Robert Jarzmik [this message]
2015-05-03 18:47           ` Robert Jarzmik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vbg9v6qh.fsf@belgarion.home \
    --to=robert.jarzmik@free.fr \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=daniel@zonque.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.