From: Mark Brown <broonie@kernel.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, Fabio Estevam <festevam@gmail.com>,
kernel@pengutronix.de
Subject: Re: [PATCH v2 2/4] ASoC: imx-sgtl5000: Let the code clock be a mandatory binding
Date: Thu, 25 Apr 2013 12:01:27 +0100 [thread overview]
Message-ID: <20130425110127.GR5019@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130425051654.GB1389@S2101-09.ap.freescale.net>
[-- Attachment #1.1: Type: text/plain, Size: 486 bytes --]
On Thu, Apr 25, 2013 at 01:16:55PM +0800, Shawn Guo wrote:
> On Wed, Apr 24, 2013 at 11:54:44AM -0300, Fabio Estevam wrote:
> > - Rebased against Shawn's tree and remove mx53qsb clock fix, as it was already
> > applied on Shawn's tree
> It seems that you expect the patch to go via my tree? In that case, I
> need Mark's ACK.
Well, it's a bit late for ARM changes to go in so I guess it'll be
sorted out after the merge window anyway and can be applied to the
ASoC tree after that?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-04-25 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 14:54 [PATCH v2 1/4] ASoC: imx-sgtl5000: Do not enter the error path on success Fabio Estevam
2013-04-24 14:54 ` [PATCH v2 2/4] ASoC: imx-sgtl5000: Let the code clock be a mandatory binding Fabio Estevam
2013-04-25 5:16 ` Shawn Guo
2013-04-25 11:01 ` Mark Brown [this message]
2013-04-25 14:35 ` Shawn Guo
2013-05-01 16:53 ` Mark Brown
2013-05-02 2:04 ` Shawn Guo
2013-04-24 14:54 ` [PATCH v2 3/4] ASoC: imx-sgtl5000: Do a sanity check on the codec clock Fabio Estevam
2013-04-25 5:20 ` Shawn Guo
2013-04-24 14:54 ` [PATCH v2 4/4] ASoC: imx-sgtl5000: Convert to devm_clk_get() Fabio Estevam
2013-04-25 5:21 ` Shawn Guo
2013-04-25 5:05 ` [PATCH v2 1/4] ASoC: imx-sgtl5000: Do not enter the error path on success Shawn Guo
2013-04-25 10:41 ` 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=20130425110127.GR5019@opensource.wolfsonmicro.com \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=shawn.guo@linaro.org \
/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