From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ricardo Neri <rneri@dextratech.com>
Cc: tomi.valkeinen@ti.com, lrg@ti.com, tony@atomide.com,
peter.ujfalusi@ti.com, dzuniga@dextratech.com,
linux-omap@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [RESEND PATCH v3 1/5] ARM: OMAP4+: HDMI: Rename platform devices for ASoC drivers
Date: Mon, 14 Jan 2013 08:19:05 +0900 [thread overview]
Message-ID: <20130113231904.GK5041@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1357341987-3327-2-git-send-email-rneri@dextratech.com>
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
On Fri, Jan 04, 2013 at 05:26:23PM -0600, Ricardo Neri wrote:
> Assign more logical and meaningful names to the platform devices used
> by ASoC OMAP HDMI drivers.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-13 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 23:26 [RESEND PATCH v3 0/5] ARM: OMAP4+: HDMI: Update platform devices for audio Ricardo Neri
2013-01-04 23:26 ` [RESEND PATCH v3 1/5] ARM: OMAP4+: HDMI: Rename platform devices for ASoC drivers Ricardo Neri
2013-01-13 23:19 ` Mark Brown [this message]
2013-01-04 23:26 ` [RESEND PATCH v3 2/5] ARM: OMAP4: Assign IDs to DSS HDMI devices Ricardo Neri
2013-01-25 14:44 ` [alsa-devel] " Sebastien Guiriec
2013-01-25 16:23 ` Ricardo Neri
2013-01-04 23:26 ` [RESEND PATCH v3 3/5] ARM4: OMAP4+: HDMI: Relocate devices for audio codec and card Ricardo Neri
2013-01-04 23:26 ` [RESEND PATCH v3 4/5] ARM: OMAP4+: HDMI: Relocate the device for audio interface Ricardo Neri
2013-01-04 23:26 ` [RESEND PATCH v3 5/5] ARM: OMAP4+: HDMI: Refine the DMA port resource for audio Ricardo Neri
2013-01-13 23:20 ` 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=20130113231904.GK5041@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dzuniga@dextratech.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=rneri@dextratech.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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).