From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Fix reg_cache_size for stac9766
Date: Mon, 5 Dec 2011 13:31:28 +0000 [thread overview]
Message-ID: <20111205133128.GN11150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1323050764.6086.1.camel@phoenix>
On Mon, Dec 05, 2011 at 10:06:04AM +0800, Axel Lin wrote:
> reg_cache_size is supposed to be the number of elements in the register cache,
> not the size in bytes.
Applied, though note that in this case as the register values are 8 bits
the two numbers are exactly the same so this is a coding style fix only
(but still useful!).
next prev parent reply other threads:[~2011-12-05 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 2:06 [PATCH] ASoC: Fix reg_cache_size for stac9766 Axel Lin
2011-12-05 13:31 ` Mark Brown [this message]
2011-12-05 14:12 ` Axel Lin
2011-12-05 14:18 ` 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=20111205133128.GN11150@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=lars@metafoo.de \
--cc=lrg@ti.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).