From: Lars-Peter Clausen <lars@metafoo.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, broonie@kernel.org,
linus.walleij@linaro.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation
Date: Tue, 03 Dec 2013 12:55:42 +0100 [thread overview]
Message-ID: <529DC6BE.3080607@metafoo.de> (raw)
In-Reply-To: <1386066427-6862-1-git-send-email-lee.jones@linaro.org>
On 12/03/2013 11:27 AM, Lee Jones wrote:
> If booting with full DT support (i.e. DMA too, the last piece of the
> puzzle), then we don't need to use the compatible_request_channel call
> back or require some of the historical bumph which probably isn't
> required by a platform data start-up now either. This will also be
> ripped out in upcoming commits.
>
> Cc: alsa-devel@alsa-project.org
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Strictly speaking you do not need the second config, but well considering
that this will all hopefully be removed soon anyway it should be fine.
Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
next prev parent reply other threads:[~2013-12-03 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 10:27 [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-12-03 10:27 ` [PATCH 2/2] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-12-03 11:55 ` Lars-Peter Clausen [this message]
2013-12-03 12:04 ` [alsa-devel] [PATCH 1/2] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-12-03 12:15 ` Lars-Peter Clausen
2013-12-03 12:24 ` [alsa-devel] " Lars-Peter Clausen
2013-12-03 12:29 ` Lee Jones
2013-12-03 15:07 ` Mark Brown
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=529DC6BE.3080607@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).