From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/5] Fixes for the pxa common clocks
Date: Fri, 07 Nov 2014 23:05:48 +0100 [thread overview]
Message-ID: <87389uy8cj.fsf@free.fr> (raw)
In-Reply-To: <87oasu6oe5.fsf@free.fr> (Robert Jarzmik's message of "Thu, 30 Oct 2014 07:51:46 +0100")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Robert Jarzmik <robert.jarzmik@free.fr> writes:
>
>> Hi Mike, Arnd, Haojian,
>>
>> Here are all the fixes I had gathered so far on pxa clocks serie.
>>
>> Amongst these :
>> - only patch 1/5 is a really required fix
>> - patches 2/5 and 3/5, after review, could go to the next merge window
>> - patch 4/5 should be carefully reviewed by pxa and arm people, but not merged
>> until pxa25x support is in place.
>> - patch 5/5 should only be considered if ever Tomeu's changes get in.
>>
>> I'm sending these to give us time to review ahead of time. And of course they
>> have only been tested on a single pxa27x platform, but once my environment is
>> ready, I'll pass a full build test on all PXA platform.
>>
>> Cheers.
>
> Hi Mike,
>
> Did you had a chance to look at those patches (1/5 to 3/5) ?
Mike ?
--
Robert
prev parent reply other threads:[~2014-11-07 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 23:07 [PATCH v1 0/5] Fixes for the pxa common clocks Robert Jarzmik
2014-10-06 23:07 ` [PATCH v1 1/5] clk: pxa: fix pxa27x CCCR bit usage Robert Jarzmik
2014-11-17 19:25 ` Mike Turquette
2014-10-06 23:07 ` [PATCH v1 2/5] clk: pxa: declare init function and data __init Robert Jarzmik
2014-10-06 23:07 ` [PATCH v1 3/5] clk: pxa: keep clocks initialization separated per variant Robert Jarzmik
2014-11-17 19:32 ` Mike Turquette
2014-10-06 23:08 ` [PATCH v1 4/5] DON'T MERGE ME: arm: pxa: change clocks init sequence Robert Jarzmik
2014-10-06 23:08 ` [PATCH v1 5/5] DON'T MERGE ME: clk: pxa: migrate to the clk_core API Robert Jarzmik
2014-10-30 6:51 ` [PATCH v1 0/5] Fixes for the pxa common clocks Robert Jarzmik
2014-11-07 22:05 ` Robert Jarzmik [this message]
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=87389uy8cj.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--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.