From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V02 0/5] dmaengine: New 'universal' API for requesting channel
Date: Mon, 14 Dec 2015 12:32:23 +0100 [thread overview]
Message-ID: <1533685.J1X7ETnh7U@wuerfel> (raw)
In-Reply-To: <1450092140-31602-1-git-send-email-peter.ujfalusi@ti.com>
On Monday 14 December 2015 13:22:15 Peter Ujfalusi wrote:
>
> Changes since v1:
> - Added Reviewed-by from Andy for patch 1-2, I decided to not add the reviewed-by
> to patch 3 due to the changes since v1
> - patch for omap-dma to support passing the filter setup to the core
> - dma_request_slave_channel_reason() remeved and it is now defines as
> dma_request_chan()
> - Print of warning removed when DT or ACPI lookup fails and we are going to
> Fallback to legacy lookup
> - members of struct dma_filter has been revised for simplicity.
Whole series
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Looks all great to me now.
prev parent reply other threads:[~2015-12-14 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 11:22 [PATCH V02 0/5] dmaengine: New 'universal' API for requesting channel Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 1/5] dmaengine: core: Skip mask matching when it is not provided to private_candidate Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 2/5] dmaengine: core: Move and merge the code paths using private_candidate Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 3/5] dmaengine: core: Introduce new, universal API to request a channel Peter Ujfalusi
2015-12-14 13:04 ` kbuild test robot
2015-12-14 20:39 ` Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 4/5] dmaengine: edma: Add support for DMA filter mapping to slave devices Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 5/5] dmaengine: omap-dma: " Peter Ujfalusi
2015-12-14 11:32 ` Arnd Bergmann [this message]
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=1533685.J1X7ETnh7U@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox