From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, dong.aisheng@linaro.org,
DWinner@tc-helicon.com, shawn.guo@linaro.org
Subject: Re: [PATCH v4 2/2] ASoC: mxs-saif: Remove platform data
Date: Wed, 14 Nov 2012 10:02:07 +0900 [thread overview]
Message-ID: <20121114010205.GB4415@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAOMZO5DCjg+SxDDxUD1cxbYyu5QdohmoXQs4XtfgbFfoW59ePQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 520 bytes --]
On Tue, Nov 13, 2012 at 10:25:06AM -0200, Fabio Estevam wrote:
> fix/mxs branch misses commit 730963f81 (ASoC: mxs-saif: Use devm_clk_get()).
> This patch applies cleanly against your for-next and also against linux-next.
That commit appears to have been added somewhere prior to v3.6 so should
be in mainline now in which case it's surprising that it's not in a
branch based off v3.7-rc3, and indeed when I look at both the fix/mxs
branch and mainline I can see the commit. This suggests that it isn't
the problem.
[-- 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:[~2012-11-14 1:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 17:57 [PATCH v2 1/2] ASoC: mxs-saif: Fix channel swap for 24-bit format Fabio Estevam
2012-11-01 17:57 ` [PATCH v4 2/2] ASoC: mxs-saif: Remove platform data Fabio Estevam
2012-11-02 15:03 ` Mark Brown
2012-11-13 12:25 ` Fabio Estevam
2012-11-14 1:02 ` Mark Brown [this message]
2012-11-01 21:59 ` [PATCH v2 1/2] ASoC: mxs-saif: Fix channel swap for 24-bit format Dong Aisheng
2012-11-02 15:03 ` 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=20121114010205.GB4415@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=DWinner@tc-helicon.com \
--cc=alsa-devel@alsa-project.org \
--cc=dong.aisheng@linaro.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--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