From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: Sebastian Hesselbarh <sebastian.hesselbarth@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Common clock framework for external clock generators
Date: Mon, 14 May 2012 19:12:40 +0100 [thread overview]
Message-ID: <20120514181240.GI25668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJOA=zOXh_+HbtSr8cXXNJWCWJroC2Cy+62y9nx7tdH4ZbhXKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Mon, May 14, 2012 at 11:08:58AM -0700, Turquette, Mike wrote:
> Seems like the clk_unregister patch fell through the cracks. My
> mistake. I'm going to be sending another pull request to arm-soc with
> Orion/Kirkwood support. I'll add your patch in at that time.
Ah, great. I dropped usage from the wm831x driver I just posted, I'd
rather get that merged if I can, but I can easily add it back - I'll
either roll it in to the next version or send a followup if this version
is basically OK.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-14 18:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 1:11 [RFC] Common clock framework for external clock generators Sebastian Hesselbarh
2012-05-13 12:29 ` Mark Brown
2012-05-13 16:30 ` Sebastian Hesselbarh
2012-05-13 16:43 ` Mark Brown
2012-05-13 17:11 ` Sebastian Hesselbarh
2012-05-13 17:16 ` Mark Brown
2012-05-14 18:08 ` Turquette, Mike
2012-05-14 18:12 ` Mark Brown [this message]
2012-10-11 8:34 ` Daniel Mack
2012-10-11 16:00 ` Sebastian Hesselbarth
2012-10-12 18:17 ` Daniel Mack
2012-10-14 10:59 ` Sebastian Hesselbarth
2012-10-14 10:59 ` Sebastian Hesselbarth
2012-10-14 11:13 ` Daniel Mack
2012-10-14 11:13 ` Daniel Mack
2012-10-14 16:16 ` Sebastian Hesselbarth
2012-10-14 16:16 ` Sebastian Hesselbarth
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=20120514181240.GI25668@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=sebastian.hesselbarth@googlemail.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.