From: Vinod Koul <vinod.koul@intel.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH 00/26] OMAP dma engine rework
Date: Wed, 2 Apr 2014 22:02:01 +0530 [thread overview]
Message-ID: <20140402163201.GT1976@intel.com> (raw)
In-Reply-To: <20140329181306.GE27282@n2100.arm.linux.org.uk>
On Sat, Mar 29, 2014 at 06:13:06PM +0000, Russell King - ARM Linux wrote:
> On Tue, Mar 18, 2014 at 09:18:45PM +0530, Vinod Koul wrote:
> > On Mon, Feb 10, 2014 at 09:25:31PM +0530, Russell King - ARM Linux wrote:
> > > This is the current set of patches for the OMAP DMA engine rework,
> > > which should now work correctly on OMAP1 platforms thanks to Tony's
> > > testing.
> > >
> > > It would be good to get this validated by others across a range of
> > > OMAP platforms, and queued up for the next merge window, so it can
> > > be built upon.
> > >
> > > Acks appreciated, and once sufficient have been added, I'll send a
> > > pull request for this to Vinod.
> > So is this series finalized. I havent seen the pull request for this or did i
> > miss it!
>
> Gah, missed this.
>
> As nothing has changed with it since 18th February, which was to add
> Tony's ack to the set. I think it's as good as it's going to get for
> the time being. It's also been in linux-next all this time, and no
> one has reported any problems. I'll need to sort out a proper pull
> request for it ASAP... or something. An alternate solution would be
> your blessing for this set.
Okay in that case pls send with my ACK.
Thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/26] OMAP dma engine rework
Date: Wed, 2 Apr 2014 22:02:01 +0530 [thread overview]
Message-ID: <20140402163201.GT1976@intel.com> (raw)
In-Reply-To: <20140329181306.GE27282@n2100.arm.linux.org.uk>
On Sat, Mar 29, 2014 at 06:13:06PM +0000, Russell King - ARM Linux wrote:
> On Tue, Mar 18, 2014 at 09:18:45PM +0530, Vinod Koul wrote:
> > On Mon, Feb 10, 2014 at 09:25:31PM +0530, Russell King - ARM Linux wrote:
> > > This is the current set of patches for the OMAP DMA engine rework,
> > > which should now work correctly on OMAP1 platforms thanks to Tony's
> > > testing.
> > >
> > > It would be good to get this validated by others across a range of
> > > OMAP platforms, and queued up for the next merge window, so it can
> > > be built upon.
> > >
> > > Acks appreciated, and once sufficient have been added, I'll send a
> > > pull request for this to Vinod.
> > So is this series finalized. I havent seen the pull request for this or did i
> > miss it!
>
> Gah, missed this.
>
> As nothing has changed with it since 18th February, which was to add
> Tony's ack to the set. I think it's as good as it's going to get for
> the time being. It's also been in linux-next all this time, and no
> one has reported any problems. I'll need to sort out a proper pull
> request for it ASAP... or something. An alternate solution would be
> your blessing for this set.
Okay in that case pls send with my ACK.
Thanks
--
~Vinod
next prev parent reply other threads:[~2014-04-02 17:06 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 15:55 [PATCH 00/26] OMAP dma engine rework Russell King - ARM Linux
2014-02-10 15:55 ` Russell King - ARM Linux
2014-02-10 15:55 ` [PATCH 01/26] dmaengine: omap-dma: use devm_kzalloc() to allocate omap_dmadev Russell King
2014-02-10 15:55 ` Russell King
2014-02-10 15:56 ` [PATCH 02/26] dmaengine: omap-dma: provide a hook to get the underlying DMA platform ops Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 03/26] dmaengine: omap-dma: program hardware directly Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 04/26] dmaengine: omap-dma: consolidate writes to DMA registers Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 05/26] dmaengine: omap-dma: control start/stop directly Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 06/26] dmaengine: omap-dma: move reading of dma position to omap-dma.c Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 07/26] dmaengine: omap-dma: consolidate setup of CSDP Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 08/26] dmaengine: omap-dma: consolidate setup of CCR Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 09/26] dmaengine: omap-dma: provide register definitions Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 10/26] dmaengine: omap-dma: move CCR buffering disable errata out of the fast path Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 11/26] dmaengine: omap-dma: consolidate clearing channel status register Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 12/26] dmaengine: omap-dma: improve efficiency loading C.SA/C.EI/C.FI registers Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:56 ` [PATCH 13/26] dmaengine: omap-dma: move clnk_ctrl setting to preparation functions Russell King
2014-02-10 15:56 ` Russell King
2014-02-10 15:57 ` [PATCH 14/26] dmaengine: omap-dma: move barrier to omap_dma_start_desc() Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 15/26] dmaengine: omap-dma: use cached CCR value when enabling DMA Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 16/26] dmaengine: omap-dma: provide register read/write functions Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 17/26] dmaengine: omap-dma: cleanup errata 3.3 handling Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 18/26] ARM: omap: remove references to disable_irq_lch Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 19/26] ARM: omap: remove almost-const variables Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 20/26] ARM: omap: clean up DMA register accesses Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 21/26] ARM: omap: dma: get rid of errata global Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 22/26] ARM: omap: move dma channel allocation into plat-omap code Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 23/26] ARM: omap: dma: get rid of 'p' allocation and clean up Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:57 ` [PATCH 24/26] dmaengine: omap-dma: move register read/writes into omap-dma.c Russell King
2014-02-10 15:57 ` Russell King
2014-02-10 15:58 ` [PATCH 25/26] dmaengine: omap-dma: move IRQ handling to omap-dma Russell King
2014-02-10 15:58 ` Russell King
2014-02-10 15:58 ` [PATCH 26/26] dmaengine: omap-dma: more consolidation of CCR register setup Russell King
2014-02-10 15:58 ` Russell King
2014-02-13 17:22 ` [PATCH 00/26] OMAP dma engine rework Tony Lindgren
2014-02-13 17:22 ` Tony Lindgren
2014-02-14 12:54 ` Sricharan R
2014-02-14 12:54 ` Sricharan R
2014-03-18 15:48 ` Vinod Koul
2014-03-18 15:48 ` Vinod Koul
2014-03-29 18:13 ` Russell King - ARM Linux
2014-03-29 18:13 ` Russell King - ARM Linux
2014-04-02 16:32 ` Vinod Koul [this message]
2014-04-02 16:32 ` Vinod Koul
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=20140402163201.GT1976@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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.