From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] DMA Engine: switch PL330 driver to non-irq-safe runtime PM
Date: Fri, 13 Jan 2017 18:00:42 +0100 [thread overview]
Message-ID: <3102129.expA2ZvqTx@wuerfel> (raw)
In-Reply-To: <60596eee-12a9-58f3-387e-145a5bc28aaa@samsung.com>
On Friday, January 13, 2017 3:12:57 PM CET Marek Szyprowski wrote:
> On 2017-01-13 14:59, Ulf Hansson wrote:
> > On 13 January 2017 at 08:26, Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> > I did only a brief review so far, particularly concentrating on the
> > changes for device links and runtime PM. I like it!
> >
> > Perhaps we can get someone like Arnd/Vinod to comment in general idea
> > from a DT and DMA slave channel point of view. I don't know that stuff
> > good enough to give good opinion.
>
> Arnd already said that it looks good:
> http://www.spinics.net/lists/dmaengine/msg12186.html
Rihgt, feel free to add my
Acked-by: Arnd Bergmann <arnd@arndb.de>
Arnd
prev parent reply other threads:[~2017-01-13 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170113072651eucas1p2b7487d97894de93daab24adb6745087c@eucas1p2.samsung.com>
2017-01-13 7:26 ` [PATCH v4 0/4] DMA Engine: switch PL330 driver to non-irq-safe runtime PM Marek Szyprowski
2017-01-13 7:26 ` [PATCH v4 1/4] dmaengine: pl330: remove pdata based initialization Marek Szyprowski
2017-01-13 13:20 ` Krzysztof Kozlowski
2017-01-13 7:26 ` [PATCH v4 2/4] dmaengine: Forward slave device pointer to of_xlate callback Marek Szyprowski
2017-01-13 7:26 ` [PATCH v4 3/4] dmaengine: pl330: Store pointer to slave device Marek Szyprowski
2017-01-13 7:26 ` [PATCH v4 4/4] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski
2017-01-13 14:22 ` Krzysztof Kozlowski
2017-01-13 13:59 ` [PATCH v4 0/4] DMA Engine: switch PL330 driver to non-irq-safe " Ulf Hansson
2017-01-13 14:12 ` Marek Szyprowski
2017-01-13 14:41 ` Ulf Hansson
2017-01-13 17:00 ` 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=3102129.expA2ZvqTx@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