From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fabio Estevam <fabio.estevam@freescale.com>
Cc: manuel.lauss@googlemail.com, lee.jones@linaro.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/3] ASoC: Revert "ASoC: mc13783: Provide codec->control_data"
Date: Tue, 11 Sep 2012 08:21:30 +0800 [thread overview]
Message-ID: <20120911002128.GG30699@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1347293410-23683-1-git-send-email-fabio.estevam@freescale.com>
On Mon, Sep 10, 2012 at 01:10:08PM -0300, Fabio Estevam wrote:
> Since commit 98d3088e5 (SoC: core: Fix check before defaulting to regmap)
> , it is not necessary to provide codec->control_data anymore.
Applied all, thanks.
prev parent reply other threads:[~2012-09-11 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 16:10 [PATCH 1/3] ASoC: Revert "ASoC: mc13783: Provide codec->control_data" Fabio Estevam
2012-09-10 16:10 ` [PATCH 2/3] ASoC: Revert "ASoC: ab8500: Inform SoC Core that we have our own I/O arrangements" Fabio Estevam
2012-09-10 16:10 ` [PATCH 3/3] Revert "ASoC: AC97 doesn't use regmap by default" Fabio Estevam
2012-09-11 0:21 ` Mark Brown [this message]
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=20120911002128.GG30699@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@freescale.com \
--cc=lee.jones@linaro.org \
--cc=manuel.lauss@googlemail.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).