From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Fix comment width in soc-cache.c
Date: Tue, 05 Apr 2011 08:34:18 +0100 [thread overview]
Message-ID: <1301988858.14075.108.camel@vega> (raw)
In-Reply-To: <1301907384-13094-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Mon, 2011-04-04 at 17:56 +0900, Mark Brown wrote:
> Lines should be less than 80 columns.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/soc-cache.c | 9 +++++----
> 1 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/sound/soc/soc-cache.c b/sound/soc/soc-cache.c
> index 5655fce..3e7f691 100644
> --- a/sound/soc/soc-cache.c
> +++ b/sound/soc/soc-cache.c
> @@ -393,10 +393,11 @@ static int snd_soc_16_16_spi_write(void *control_data, const char *data,
> #define snd_soc_16_16_spi_write NULL
> #endif
>
> -/* Primitive bulk write support for soc-cache. The data pointed to by `data' needs
> - * to already be in the form the hardware expects including any leading register specific
> - * data. Any data written through this function will not go through the cache as it
> - * only handles writing to volatile or out of bounds registers.
> +/* Primitive bulk write support for soc-cache. The data pointed to by
> + * `data' needs to already be in the form the hardware expects
> + * including any leading register specific data. Any data written
> + * through this function will not go through the cache as it only
> + * handles writing to volatile or out of bounds registers.
> */
> static int snd_soc_hw_bulk_write_raw(struct snd_soc_codec *codec, unsigned int reg,
> const void *data, size_t len)
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-04-05 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 8:56 [PATCH] ASoC: Fix comment width in soc-cache.c Mark Brown
2011-04-05 7:34 ` 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=1301988858.14075.108.camel@vega \
--to=lrg@slimlogic.co.uk \
--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 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).