From: Mark Brown <broonie@kernel.org>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, linux-spi@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Ben Dooks <ben-linux@fluff.org>,
Jaroslav Kysela <perex@perex.cz>,
Kukjin Kim <kgene.kim@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mike Turquette <mturquette@linaro.org>,
Padmavathi Venna <padma.v@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Sachin Kamat <sachin.kamat@linaro.org>,
Sangbeom Kim <sbkim73@samsung.com>, Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH v2 2/8] ASoC: Samsung: Do not require legacy DMA API in case of S3C64XX
Date: Thu, 17 Oct 2013 11:34:09 +0100 [thread overview]
Message-ID: <20131017103409.GM2443@sirena.org.uk> (raw)
In-Reply-To: <1381950659-12703-3-git-send-email-tomasz.figa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
On Wed, Oct 16, 2013 at 09:10:53PM +0200, Tomasz Figa wrote:
> With support for amba-pl08x driver, on S3C64xx the generic DMA engine
> API can be used instead of the private s3c-dma interface.
>
> Signed-off-by: Tomasz Figa <tomasz.figa@gmail.com>
Acked-by: Mark Brown <broonie@linaro.org>
in case we can get this into v3.13.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-17 10:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 19:10 [PATCH v2 0/8] ARM: s3c64xx: Let amba-pl08x driver handle DMA Tomasz Figa
2013-10-16 19:10 ` [PATCH v2 1/8] spi: s3c64xx: Do not require legacy DMA API in case of S3C64XX Tomasz Figa
2013-10-17 10:33 ` Mark Brown
2013-10-16 19:10 ` [PATCH v2 2/8] ASoC: Samsung: " Tomasz Figa
2013-10-17 10:34 ` Mark Brown [this message]
2013-10-16 19:10 ` [PATCH v2 3/8] ARM: s3c64xx: Add support for DMA using generic amba-pl08x driver Tomasz Figa
2013-10-16 19:10 ` [PATCH v2 4/8] clk: samsung: s3c64xx: Add aliases for DMA clocks Tomasz Figa
2013-10-21 12:11 ` Mike Turquette
2013-10-16 19:10 ` [PATCH v2 5/8] ARM: s3c64xx: Remove legacy DMA driver Tomasz Figa
2013-10-16 19:10 ` [PATCH v2 6/8] clk: samsung: s3c64xx: Remove clock aliases of old " Tomasz Figa
[not found] ` <1381950659-12703-7-git-send-email-tomasz.figa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-10-21 12:12 ` Mike Turquette
2013-10-16 19:10 ` [PATCH v2 7/8] spi: s3c64xx: Always select S3C64XX_PL080 when ARCH_S3C64XX is enabled Tomasz Figa
2013-10-16 19:10 ` [PATCH v2 8/8] ASoC: Samsung: " Tomasz Figa
2013-10-17 10:22 ` [PATCH v2 0/8] ARM: s3c64xx: Let amba-pl08x driver handle DMA Mark Brown
[not found] ` <20131017102201.GK2443-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-10-20 21:04 ` Kukjin Kim
[not found] ` <52644563.1000203-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-11-20 12:31 ` Mark Brown
[not found] ` <20131120123152.GZ2674-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-12-04 21:39 ` Olof Johansson
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=20131017103409.GM2443@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=kgene.kim@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@linaro.org \
--cc=padma.v@samsung.com \
--cc=perex@perex.cz \
--cc=sachin.kamat@linaro.org \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.de \
--cc=tomasz.figa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox