From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C64XX: Define some additional always off clocks
Date: Fri, 2 Dec 2011 19:37:48 +0000 [thread overview]
Message-ID: <20111202193747.GC4333@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <29404566.LHT7QYyV2R@flatron>
On Fri, Dec 02, 2011 at 08:16:53PM +0100, Tomasz Figa wrote:
> I have already done all the work needed to support the whole range of clocks
> on S3C6410, but I can't find time to create and submit all the patches.
> (See: https://github.com/tom3q/spica-3.0/commits/android-
> s3c64xx/arch/arm/mach-s3c64xx/clock.c if you are interested.)
A lot of good stuff in there - it's a bit of a shame you've not signed
off any of the patches there.
next prev parent reply other threads:[~2011-12-02 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 15:57 [PATCH] ARM: S3C64XX: Define some additional always off clocks Mark Brown
2011-12-02 19:16 ` Tomasz Figa
2011-12-02 19:37 ` Mark Brown [this message]
2011-12-02 19:45 ` Tomasz Figa
2011-12-02 21:13 ` Mark Brown
2011-12-02 21:31 ` Tomasz Figa
2011-12-02 22:25 ` Mark Brown
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=20111202193747.GC4333@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--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 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).