From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] ASoC: Move register I/O code into a separate file
Date: Mon, 13 Jun 2011 18:44:05 +0100 [thread overview]
Message-ID: <4DF64C65.9040100@ti.com> (raw)
In-Reply-To: <1307983867-5084-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On 13/06/11 17:51, Mark Brown wrote:
> For clarity and to help ongoing refactoring in this area create a new file
> to contain the physical I/O functions, separating them out from the cache
> operations.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/Makefile | 3 +-
> sound/soc/soc-cache.c | 380 ----------------------------------------------
> sound/soc/soc-io.c | 399 +++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 401 insertions(+), 381 deletions(-)
> create mode 100644 sound/soc/soc-io.c
>
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-06-13 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 16:51 [PATCH] ASoC: Move register I/O code into a separate file Mark Brown
2011-06-13 17:44 ` Liam Girdwood [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=4DF64C65.9040100@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--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 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.