From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org, Stephen Warren <swarren@nvidia.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCHv2] ASoC: Fix wrong data type access in a few codec drivers
Date: Mon, 16 May 2011 09:07:34 -0700 [thread overview]
Message-ID: <20110516160732.GB6957@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1305303412-31837-1-git-send-email-jhnikula@gmail.com>
On Fri, May 13, 2011 at 07:16:52PM +0300, Jarkko Nikula wrote:
> Commit fafd217 ("ASoC: Store a list of widgets in a DAPM mux/mixer kcontrol")
> changed the control private data type that is passed to snd_soc_cnew when
> creating dapm mixer and mux controls. Commit did not update a few codec
> drivers that are using their own put callbacks and thus are accessing a
> wrong data type.
Applied, thanks.
prev parent reply other threads:[~2011-05-16 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 16:16 [PATCHv2] ASoC: Fix wrong data type access in a few codec drivers Jarkko Nikula
2011-05-13 16:40 ` Stephen Warren
2011-05-16 13:43 ` Liam Girdwood
2011-05-16 16:07 ` 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=20110516160732.GB6957@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=lrg@ti.com \
--cc=swarren@nvidia.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).