From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Padmavathi Venna <padma.v@samsung.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org,
devicetree-discuss@lists.ozlabs.org, padma.kvr@gmail.com,
sbkim73@samsung.com, lrg@ti.com, tiwai@suse.de,
ben-linux@fluff.org, kgene.kim@samsung.com, ben@simtec.co.uk,
lrg@slimlogic.co.uk, jassisinghbrar@gmail.com,
anarsoul@gmail.com, graeme.gregory@wolfsonmicro.com,
philipp.zabel@gmail.com, dgreenday@gmail.com,
chripell@evolware.org, mcuelenaere@gmail.com
Subject: Re: [PATCH V2 1/2] ASoC: Samsung: Do not register samsung audio dma device as pdev
Date: Fri, 7 Dec 2012 15:46:46 +0900 [thread overview]
Message-ID: <20121207064644.GI26070@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1354765837-3469-2-git-send-email-padma.v@samsung.com>
On Thu, Dec 06, 2012 at 09:20:36AM +0530, Padmavathi Venna wrote:
> Previously, the ASoC 'platform' (PCM/DMA) object was instantiated via a
> platform_device. This didn't represent the hardware well, since there
> was no separate hardware associated with this platform_device; it was a
> virtual device with sole purpose to call snd_soc_register_platform().
Looks good however this doesn't apply against my topic/samsung branch -
can you please check if I need anything from Kukjin's tree? Though I
guess the easiest thing is just to wait until the merge window is over,
we're near to the next release.
next prev parent reply other threads:[~2012-12-07 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 3:50 [PATCH V2 0/2] ASoC: Samsung: Remove platform device support Padmavathi Venna
2012-12-06 3:50 ` [PATCH V2 1/2] ASoC: Samsung: Do not register samsung audio dma device as pdev Padmavathi Venna
2012-12-07 6:46 ` Mark Brown [this message]
2012-12-07 8:17 ` Padma Venkat
2012-12-06 3:50 ` [PATCH V3 2/2] ASoC: SMDK: WM8994: Add device tree support for machine file Padmavathi Venna
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=20121207064644.GI26070@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@gmail.com \
--cc=ben-linux@fluff.org \
--cc=ben@simtec.co.uk \
--cc=chripell@evolware.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dgreenday@gmail.com \
--cc=graeme.gregory@wolfsonmicro.com \
--cc=jassisinghbrar@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=lrg@ti.com \
--cc=mcuelenaere@gmail.com \
--cc=padma.kvr@gmail.com \
--cc=padma.v@samsung.com \
--cc=philipp.zabel@gmail.com \
--cc=sbkim73@samsung.com \
--cc=tiwai@suse.de \
/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).