From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Zeng Zhaoming <zhaoming.zeng@freescale.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
linux-kernel@vger.kernel.org,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH] ASoC: Use SGTL5000_LINREG_VDDD_MASK instead of hardcoded mask value
Date: Fri, 21 Oct 2011 09:56:35 +0100 [thread overview]
Message-ID: <20111021085635.GD3513@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1319107769.8866.3.camel@phoenix>
On Thu, Oct 20, 2011 at 06:49:29PM +0800, Axel Lin wrote:
> We have defined SGTL5000_LINREG_VDDD_MASK in sgtl5000.h,
> use it instead of hardcoded (0x1 << 4) - 1 for the mask.
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,
Zeng Zhaoming <zhaoming.zeng@freescale.com>,
Wolfram Sang <w.sang@pengutronix.de>, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: Use SGTL5000_LINREG_VDDD_MASK instead of hardcoded mask value
Date: Fri, 21 Oct 2011 09:56:35 +0100 [thread overview]
Message-ID: <20111021085635.GD3513@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1319107769.8866.3.camel@phoenix>
On Thu, Oct 20, 2011 at 06:49:29PM +0800, Axel Lin wrote:
> We have defined SGTL5000_LINREG_VDDD_MASK in sgtl5000.h,
> use it instead of hardcoded (0x1 << 4) - 1 for the mask.
Applied, thanks.
next prev parent reply other threads:[~2011-10-21 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 10:49 [PATCH] ASoC: Use SGTL5000_LINREG_VDDD_MASK instead of hardcoded mask value Axel Lin
2011-10-20 11:02 ` Wolfram Sang
2011-10-20 11:02 ` Wolfram Sang
2011-10-20 16:54 ` Girdwood, Liam
2011-10-21 8:56 ` Mark Brown [this message]
2011-10-21 8:56 ` 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=20111021085635.GD3513@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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 \
--cc=zhaoming.zeng@freescale.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 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.