linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Make the managed clk functions generically available
Date: Wed, 12 Sep 2012 22:43:07 +0200	[thread overview]
Message-ID: <5050F3DB.1050202@metafoo.de> (raw)
In-Reply-To: <504FE633.2090304@snapgear.com>

On 09/12/2012 03:32 AM, Greg Ungerer wrote:
> On 12/09/12 00:50, Artem Bityutskiy wrote:
>> On Tue, 2012-09-11 at 16:44 +0200, Lars-Peter Clausen wrote:
>>> On 09/10/2012 02:39 AM, Russell King - ARM Linux wrote:
>>>> On Mon, Sep 10, 2012 at 08:20:21AM +0800, Mark Brown wrote:
>>>>> [...]
>>>>> OK, that's what I'd thought was going on - it was the fact that you'd
>>>>> just acked the patch rather than asked for it to go to the patch
>>>>> tracker
>>>>> or something which made me wonder if things had changed.
>>>>
>>>> I kind'a forgot because it's been soo long since I took any of those
>>>> patches...
>>>
>>> Ok, what's the plan? Should I add this patch to the patch tracker?
>>
>> I'd propose to send it to Linus for v3.6 even.
> 
> If we do this can we make a decision quickly on it.
> 
> I need to fix a regression on some ColdFire parts for 3.6. I either need
> to use this clk patch, which fixes my problem, or a specific patch for the
> ColdFire clk code http://marc.info/?l=linux-m68k&m=134725225823437&w=2
> 

I wouldn't mind having this merged sooner rather than later, there is at least
one driver in next which is currently broken due to the missing devm_clk_get.
Russell what's your plan for the patch? Maybe under the given circumstances it
makes sense to let it go through the m68k tree.

- Lars

  reply	other threads:[~2012-09-12 20:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 15:01 [PATCH] clk: Make the managed clk functions generically available Lars-Peter Clausen
2012-09-09 20:57 ` Russell King - ARM Linux
2012-09-09 23:50 ` Mark Brown
2012-09-10  0:15   ` Russell King - ARM Linux
2012-09-10  0:20     ` Mark Brown
2012-09-10  0:39       ` Russell King - ARM Linux
2012-09-11 14:44         ` Lars-Peter Clausen
2012-09-11 14:50           ` Artem Bityutskiy
2012-09-12  1:32             ` Greg Ungerer
2012-09-12 20:43               ` Lars-Peter Clausen [this message]
2012-09-15 21:31                 ` Russell King - ARM Linux
2012-09-16  0:15                   ` Greg Ungerer
2012-09-18  8:00                   ` Thierry Reding
2012-09-18  9:35                     ` Russell King - ARM Linux
2012-09-18 11:25                       ` Thierry Reding
2012-09-18 20:40                         ` Russell King - ARM Linux
2012-09-19  6:55                           ` Thierry Reding
2012-09-11 17:51           ` Russell King - ARM Linux
2012-09-10  3:10 ` Greg Ungerer

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=5050F3DB.1050202@metafoo.de \
    --to=lars@metafoo.de \
    --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).