From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] ASoC: omap-mcbsp: Use the new interface for configuring CLKR/FSR mux
Date: Thu, 22 Dec 2011 17:33:22 +0000 [thread overview]
Message-ID: <20111222173321.GC29622@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1324575106-17172-4-git-send-email-peter.ujfalusi@ti.com>
On Thu, Dec 22, 2011 at 07:31:44PM +0200, Peter Ujfalusi wrote:
> Switch using the new API to configure the 6 pin port's CLKR/FSR mux
> configuration.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2011-12-22 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 17:31 [PATCH 0/5] OMAP4: Fix CLKR/FSR mux for port with 6 pin mode Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 1/5] OMAP2/3: mcbsp: Check McBSP port number in CLKR/FSR mux callback Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 2/5] OMAP: mcbsp: Signle function for CLKR/FSR source mux configuration Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 3/5] ASoC: omap-mcbsp: Use the new interface for configuring CLKR/FSR mux Peter Ujfalusi
2011-12-22 17:33 ` Mark Brown [this message]
2011-12-22 17:31 ` [PATCH 4/5] OMAP: mcbsp: Remove old CLKR/FSR mux functions Peter Ujfalusi
2011-12-22 17:31 ` [PATCH 5/5] OMAP4: mcbsp: Callback function for McBSP4 CLKR/FSR mux selection Peter Ujfalusi
2011-12-23 10:34 ` [PATCH 0/5] OMAP4: Fix CLKR/FSR mux for port with 6 pin mode Jarkko Nikula
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=20111222173321.GC29622@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@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).