public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] clk: pxa: add pxa3xx clock driver
Date: Mon, 19 Jan 2015 23:58:14 +0100	[thread overview]
Message-ID: <87h9vmgyyh.fsf@free.fr> (raw)
In-Reply-To: <54BC3EB8.9020304@zonque.org> (Daniel Mack's message of "Mon, 19 Jan 2015 00:16:08 +0100")

Daniel Mack <daniel@zonque•org> writes:

> Hi Robert,
>
> On 01/06/2015 09:53 PM, Robert Jarzmik wrote:
>> I'd need a test to see if the pxa3xx clocks are actually working.
>> I prepared a tree in here :
>>   git fetch https://github.com/rjarzmik/linux work/clocks-pxa
>
> Very sorry for the long delay on this. I finally got around to give this
> a try, and at a glance, things look fine.
Good.

> However, I noticed a number of regressions in the PXA3xx area which I
> will investigate on later this week, one of which causing the system to
> crash on suspend. But that seems unrelated to the clocking patches, so
> I'd say they're good to go in the next merge window.
>
> Will get back once I figured out the other issues that I'm seeing.
Very well. Good hunt.

Cheers.

-- 
Robert

  reply	other threads:[~2015-01-19 22:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 20:45 [PATCH 1/2] clk: pxa: add pxa3xx clock driver Robert Jarzmik
2015-01-06 20:45 ` [PATCH 2/2] arm: pxa: switch pxa3xx to clock framework Robert Jarzmik
2015-01-06 20:53 ` [PATCH 1/2] clk: pxa: add pxa3xx clock driver Robert Jarzmik
2015-01-16 12:34   ` Robert Jarzmik
2015-01-18 23:16   ` Daniel Mack
2015-01-19 22:58     ` Robert Jarzmik [this message]
2015-01-22  7:11       ` Marek Vasut
2015-01-26 23:06 ` Robert Jarzmik
2015-01-28  1:10   ` Mike Turquette
2015-01-30 18:48     ` Robert Jarzmik

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=87h9vmgyyh.fsf@free.fr \
    --to=robert.jarzmik@free$(echo .)fr \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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