From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Songjun Wu <songjun.wu@atmel.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.de, lars@metafoo.de, fabio.estevam@freescale.com,
manuel.lauss@gmail.com, patches@opensource.wolfsonmicro.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
voice.shen@atmel.com
Subject: Re: [RFC PATCH] ASoC: wm8731: let codec to manage clock by itself
Date: Mon, 16 Mar 2015 14:53:15 +0000 [thread overview]
Message-ID: <20150316145315.GI17136@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1426126631-27240-1-git-send-email-songjun.wu@atmel.com>
On Thu, Mar 12, 2015 at 10:17:11AM +0800, Songjun Wu wrote:
> Enable WM8731 to support common clock framework.
>
> Signed-off-by: Songjun Wu <songjun.wu@atmel.com>
> ---
Looks ok to me:
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thanks,
Charles
next prev parent reply other threads:[~2015-03-16 14:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 2:17 [RFC PATCH] ASoC: wm8731: let codec to manage clock by itself Songjun Wu
2015-03-12 2:17 ` Songjun Wu
2015-03-16 14:53 ` Charles Keepax [this message]
2015-03-16 15:01 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2015-02-03 3:33 Bo Shen
2015-02-03 3:33 ` Bo Shen
2015-02-03 3:33 ` Bo Shen
2015-02-03 3:33 ` Bo Shen
2015-02-03 7:54 ` Manuel Lauss
2015-02-03 7:54 ` Manuel Lauss
2015-02-03 7:54 ` Manuel Lauss
2015-02-03 12:44 ` Mark Brown
2015-02-03 12:44 ` Mark Brown
2015-02-03 12:44 ` Mark Brown
2015-02-03 12:44 ` Mark Brown
2015-02-03 14:40 ` Manuel Lauss
2015-02-03 14:40 ` Manuel Lauss
2015-02-03 14:40 ` Manuel Lauss
2015-02-03 14:40 ` Manuel Lauss
2015-02-03 16:21 ` Mark Brown
2015-02-03 16:21 ` Mark Brown
2015-02-03 16:21 ` Mark Brown
2015-02-03 16:21 ` Mark Brown
2015-02-04 3:45 ` Bo Shen
2015-02-04 3:45 ` Bo Shen
2015-02-04 3:45 ` Bo Shen
2015-02-04 3:45 ` Bo Shen
2015-02-04 11:13 ` Mark Brown
2015-02-04 11:13 ` Mark Brown
2015-02-04 11:13 ` 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=20150316145315.GI17136@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=songjun.wu@atmel.com \
--cc=tiwai@suse.de \
--cc=voice.shen@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.