From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: [PATCH v4 3/5] OMAP4: devices: Register OMAP4 DMIC platform device
Date: Fri, 9 Dec 2011 13:03:24 -0800 [thread overview]
Message-ID: <20111209210324.GX31337@atomide.com> (raw)
In-Reply-To: <1322487943-14280-4-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [111128 05:11]:
> Add platform device registration for OMAP4 DMIC.
Thanks applying patches 3 & 4 into omap board branch.
Paul will be queuing hwmod related changes separately.
Regards,
Tony
next prev parent reply other threads:[~2011-12-09 21:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 13:45 [PATCH v4 0/5] Support for OMAP4 Digital Microphone interface Peter Ujfalusi
2011-11-28 13:45 ` [PATCH v4 1/5] OMAP4: hwmod: Add names for DMIC memory address space Peter Ujfalusi
2011-12-16 6:28 ` Paul Walmsley
2011-12-16 14:43 ` Cousson, Benoit
2011-12-19 21:51 ` Paul Walmsley
2012-01-23 11:52 ` Peter Ujfalusi
2012-01-24 8:36 ` Paul Walmsley
2012-01-24 10:01 ` Peter Ujfalusi
2012-01-25 21:23 ` Paul Walmsley
2012-02-01 7:40 ` Peter Ujfalusi
2012-02-01 19:08 ` Paul Walmsley
2012-02-02 8:32 ` Peter Ujfalusi
2011-11-28 13:45 ` [PATCH v4 2/5] ASoC: OMAP4: omap-dmic: Initial support for OMAP DMIC Peter Ujfalusi
2011-11-28 17:21 ` Mark Brown
2011-11-28 13:45 ` [PATCH v4 3/5] OMAP4: devices: Register OMAP4 DMIC platform device Peter Ujfalusi
2011-12-09 21:03 ` Tony Lindgren [this message]
2011-11-28 13:45 ` [PATCH v4 4/5] OMAP4: board-4430sdp: Register platform device for digimic codec Peter Ujfalusi
2011-11-28 13:45 ` [PATCH v4 5/5] ASoC: sdp4430: Add support for digital microphones Peter Ujfalusi
2011-11-28 17:22 ` 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=20111209210324.GX31337@atomide.com \
--to=tony@atomide.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.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;
as well as URLs for NNTP newsgroup(s).