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: Fix incorrect register cache size configuration
Date: Fri, 10 Sep 2010 22:28:50 +0100 [thread overview]
Message-ID: <20100910212850.GA20689@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1284138896-3789-1-git-send-email-dp@opensource.wolfsonmicro.com>
On Fri, Sep 10, 2010 at 06:14:56PM +0100, Dimitris Papastamos wrote:
> The reg_cache_size is the number of elements in the register cache,
> not the size of the cache itself. This is not a problem if the size
> of each element of the cache is 1 byte but it matters in any other
> case.
>
> Signed-off-by: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
Applied, thanks.
prev parent reply other threads:[~2010-09-10 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 17:14 [PATCH] ASoC: Fix incorrect register cache size configuration Dimitris Papastamos
2010-09-10 17:22 ` Liam Girdwood
2010-09-10 21:28 ` 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=20100910212850.GA20689@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