From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2] clk: pxa: export 32kHz PLL
Date: Sat, 07 Jul 2018 21:30:25 +0200 [thread overview]
Message-ID: <87d0vyg7xq.fsf@belgarion.home> (raw)
In-Reply-To: 153091032623.143105.13689700534218065371@swboyd.mtv.corp.google.com
Stephen Boyd <sboyd@kernel.org> writes:
> Quoting Robert Jarzmik (2018-07-04 22:34:10)
>> Robert Jarzmik <robert.jarzmik@free.fr> writes:
>>
>> > This clock is especially used by the RTC driver, so export it so that
>> > devicetree users can use it.
>> >
>> > Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>> > ---
>> > Since v2: fix missing parenthesis in clk-pxa25x.c and clk-pxa3xx.c
>>
>> Hi Michael and Stephen,
>>
>> Could you have a look please ?
>>
>
> I'll apply patch 1, and leave patch 2 to someone else?
As there is a dependency of patch 2 on patch 1, and with the Reviewed-by
provided by Rob, I'd appreciate you take it as well. If not, I'll queue it up
for the next cycle in my pxa tree.
Cheers.
--
Robert
next prev parent reply other threads:[~2018-07-07 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 19:41 [PATCH v4 1/2] clk: pxa: export 32kHz PLL Robert Jarzmik
2018-06-27 19:41 ` [PATCH v4 2/2] ARM: dts: pxa: fix the rtc controller Robert Jarzmik
2018-06-27 21:40 ` Rob Herring
[not found] ` <87d0w2gsa5.fsf@belgarion.home>
2018-07-06 20:52 ` [PATCH v4 1/2] clk: pxa: export 32kHz PLL Stephen Boyd
2018-07-07 19:30 ` Robert Jarzmik [this message]
2018-07-06 20:53 ` Stephen Boyd
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=87d0vyg7xq.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=devicetree@vger.kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).