From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Mike Turquette <mturquette@linaro.org>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Transition of pxa25x and pxa27x to clock framework
Date: Mon, 12 Jan 2015 12:06:25 +0100 [thread overview]
Message-ID: <87y4p8xnpq.fsf@free.fr> (raw)
In-Reply-To: <1419688528-760-1-git-send-email-robert.jarzmik@free.fr> (Robert Jarzmik's message of "Sat, 27 Dec 2014 14:55:24 +0100")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Once reviewed, I'd like this serie to go through the pxa tree. Therefore an ack
> from Mike is necesary for the last patch (add missing pxa27x clocks).
>
> This is targeted at 3.20 window.
Well, no review is good news ... or not. Mike I still need an ack for patch 4/4,
and then I'll schedule these patches for 3.21 window.
Cheers.
--
Robert
prev parent reply other threads:[~2015-01-12 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 13:55 [PATCH 0/4] Transition of pxa25x and pxa27x to clock framework Robert Jarzmik
2014-12-27 13:55 ` [PATCH 1/4] arm: pxa: change clocks init sequence Robert Jarzmik
2015-01-12 23:48 ` Mike Turquette
2014-12-27 13:55 ` [PATCH 2/4] arm: pxa: Transition pxa25x and pxa27x to clk framework Robert Jarzmik
2015-01-12 23:50 ` Mike Turquette
2014-12-27 13:55 ` [PATCH 3/4] arm: pxa: move gpio11 clock to board files Robert Jarzmik
2015-01-12 23:51 ` Mike Turquette
2014-12-27 13:55 ` [PATCH 4/4] clk: pxa: add missing pxa27x clocks for Irda and sa1100-rtc Robert Jarzmik
2015-01-12 23:52 ` Mike Turquette
2015-01-16 12:42 ` Robert Jarzmik
2015-01-12 11:06 ` 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=87y4p8xnpq.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=arnd@arndb.de \
--cc=daniel@zonque.org \
--cc=dbaryshkov@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.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