From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>, Liam Girdwood <lgirdwood@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [PATCH] ASoC: rsnd: fix clock prepare/unprepare
Date: Fri, 11 Apr 2014 11:14:04 +0100 [thread overview]
Message-ID: <20140411101404.GP6518@sirena.org.uk> (raw)
In-Reply-To: <87ob08oebr.wl%kuninori.morimoto.gx@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 630 bytes --]
On Thu, Apr 10, 2014 at 06:16:33PM -0700, Kuninori Morimoto wrote:
> From: Ben Dooks <ben.dooks@codethink.co.uk>
>
> As with the previous commit, before a clock can be used it must be prepared
> for use. Change from clk_enable() and clk_disable() to the versions of the
> calls which also prepare and un-prepare the clocks.
>
> Will fix warnings from the clock code when this is used.
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
This is written by you and sent by you but also signed off by
Morimoto-san - what's going on there?
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-04-11 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 1:16 [PATCH] ASoC: rsnd: fix clock prepare/unprepare Kuninori Morimoto
2014-04-11 10:14 ` Mark Brown [this message]
2014-04-11 11:10 ` Mark Brown
2014-04-13 23:58 ` Kuninori Morimoto
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=20140411101404.GP6518@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ben.dooks@codethink.co.uk \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.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.