From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: WM8995: Fix incorrect use of snd_soc_update_bits()
Date: Wed, 19 Jan 2011 18:49:54 +0000 [thread overview]
Message-ID: <20110119184954.GE17150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1295441728-23326-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Wed, Jan 19, 2011 at 12:55:28PM +0000, Dimitris Papastamos wrote:
> In the wm8995_set_tristate() function when updating the register
> bits use the value and not the register index as the value argument.
>
> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Applied, thanks.
prev parent reply other threads:[~2011-01-19 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 12:55 [PATCH] ASoC: WM8995: Fix incorrect use of snd_soc_update_bits() Dimitris Papastamos
2011-01-19 13:16 ` Liam Girdwood
2011-01-19 18:49 ` 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=20110119184954.GE17150@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=patches@opensource.wolfsonmicro.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).