From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] misc: atmel-ssc: prepare clock only when request
Date: Wed, 24 Sep 2014 10:07:36 +0100 [thread overview]
Message-ID: <20140924090736.GC16977@sirena.org.uk> (raw)
In-Reply-To: <1411549019-12663-1-git-send-email-voice.shen@atmel.com>
On Wed, Sep 24, 2014 at 04:56:59PM +0800, Bo Shen wrote:
> Prepare SSC clock only when request SSC channel, the clock will be
> enabled when initialize the SSC.
You should send this to the drivers/misc maintainer.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140924/8ad9d41e/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Bo Shen <voice.shen@atmel.com>
Cc: nicolas.ferre@atmel.com, boris.brezillon@free-electrons.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc: atmel-ssc: prepare clock only when request
Date: Wed, 24 Sep 2014 10:07:36 +0100 [thread overview]
Message-ID: <20140924090736.GC16977@sirena.org.uk> (raw)
In-Reply-To: <1411549019-12663-1-git-send-email-voice.shen@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 215 bytes --]
On Wed, Sep 24, 2014 at 04:56:59PM +0800, Bo Shen wrote:
> Prepare SSC clock only when request SSC channel, the clock will be
> enabled when initialize the SSC.
You should send this to the drivers/misc maintainer.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-24 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 8:56 [PATCH] misc: atmel-ssc: prepare clock only when request Bo Shen
2014-09-24 8:56 ` Bo Shen
2014-09-24 9:07 ` Mark Brown [this message]
2014-09-24 9:07 ` Mark Brown
2014-09-24 9:34 ` Bo Shen
2014-09-24 9:34 ` Bo Shen
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=20140924090736.GC16977@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.