From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: wm831x: Add initial WM831x clock driver
Date: Wed, 16 May 2012 08:53:23 +0100 [thread overview]
Message-ID: <20120516075322.GA6801@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJOA=zMRRJB5HZhQPNBbAc0+U=Rgs9v0feDqK-6VRUzGnUEbyA@mail.gmail.com>
On Tue, May 15, 2012 at 10:00:51PM -0700, Turquette, Mike wrote:
> On Mon, May 14, 2012 at 7:16 AM, Mark Brown
> > The WM831x and WM832x series of PMICs contain a flexible clocking
> > subsystem intended to provide always on and system core clocks. ?It
> > features:
> Do you plan to rebase against my clk-next branch? I've pushed your
> clk_unregister patch there.
I guess; I had removed the unregistration from the driver partly to
split out the unregistration so the driver could get merged separately.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120516/f3b57a06/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: wm831x: Add initial WM831x clock driver
Date: Wed, 16 May 2012 08:53:23 +0100 [thread overview]
Message-ID: <20120516075322.GA6801@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJOA=zMRRJB5HZhQPNBbAc0+U=Rgs9v0feDqK-6VRUzGnUEbyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
On Tue, May 15, 2012 at 10:00:51PM -0700, Turquette, Mike wrote:
> On Mon, May 14, 2012 at 7:16 AM, Mark Brown
> > The WM831x and WM832x series of PMICs contain a flexible clocking
> > subsystem intended to provide always on and system core clocks. It
> > features:
> Do you plan to rebase against my clk-next branch? I've pushed your
> clk_unregister patch there.
I guess; I had removed the unregistration from the driver partly to
split out the unregistration so the driver could get merged separately.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-16 7:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 14:16 [PATCH] clk: wm831x: Add initial WM831x clock driver Mark Brown
2012-05-14 14:16 ` Mark Brown
2012-05-16 5:00 ` Turquette, Mike
2012-05-16 5:00 ` Turquette, Mike
2012-05-16 7:53 ` Mark Brown [this message]
2012-05-16 7:53 ` Mark Brown
2012-06-12 17:09 ` Mike Turquette
2012-06-12 17:09 ` Mike Turquette
-- strict thread matches above, loose matches on Subject: below --
2012-06-04 14:44 Mark Brown
2012-06-04 14:44 ` Mark Brown
2012-05-17 9:04 Mark Brown
2012-05-17 9:04 ` Mark Brown
2012-03-22 11:33 Mark Brown
2012-03-22 11:33 ` 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=20120516075322.GA6801@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 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.