From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Dong Aisheng <B29396@freescale.com>,
linux-kernel@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH] ASoC: sgtl5000: Fix wrong mask in some snd_soc_update_bits calls
Date: Sat, 22 Oct 2011 10:36:18 +0100 [thread overview]
Message-ID: <20111022093616.GA3316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1319162083.4352.2.camel@phoenix>
On Fri, Oct 21, 2011 at 09:54:43AM +0800, Axel Lin wrote:
> Ensure all mask bits are clear before setting new value.
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Dong Aisheng <B29396@freescale.com>,
Wolfram Sang <w.sang@pengutronix.de>, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: sgtl5000: Fix wrong mask in some snd_soc_update_bits calls
Date: Sat, 22 Oct 2011 10:36:18 +0100 [thread overview]
Message-ID: <20111022093616.GA3316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1319162083.4352.2.camel@phoenix>
On Fri, Oct 21, 2011 at 09:54:43AM +0800, Axel Lin wrote:
> Ensure all mask bits are clear before setting new value.
Applied, thanks.
next prev parent reply other threads:[~2011-10-22 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 1:54 [PATCH] ASoC: sgtl5000: Fix wrong mask in some snd_soc_update_bits calls Axel Lin
2011-10-21 1:54 ` Axel Lin
2011-10-21 7:36 ` Dong Aisheng-B29396
2011-10-21 7:36 ` Dong Aisheng-B29396
2011-10-21 16:52 ` Girdwood, Liam
2011-10-21 16:52 ` Girdwood, Liam
2011-10-22 9:36 ` Mark Brown [this message]
2011-10-22 9:36 ` 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=20111022093616.GA3316@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=B29396@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=w.sang@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.