From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: imx31/of: clk: init clock controller with CLK_OF_DECLARE
Date: Tue, 20 Sep 2016 10:32:50 -0700 [thread overview]
Message-ID: <20160920173250.GB8319@codeaurora.org> (raw)
In-Reply-To: <20160919055802.dkf2rxcou44kbya5@pengutronix.de>
On 09/19, Uwe Kleine-K?nig wrote:
> Hello,
>
> On Mon, Sep 19, 2016 at 05:42:17AM +0300, Vladimir Zapolskiy wrote:
> > The change is based on v4.8.0-rc1 and plus it depends on this fixup:
> >
> > ARM: dts: imx31: fix clock control module interrupts description
> >
> > The change is tested on qemu kzm target and mx31lite board, while both
> > targets don't have DTS in upstream, I had to write simple DTS files for
> > them, because the proposed change is for i.MX31 targets with OF support.
> >
> > The second change in the series compilation time dependent on the first
> > one, while the first change apparently should break runtime execution
> > of i.MX31 boards with OF support, if both changes are applied everything
> > should be fine, regression testing on the same legacy targets does not
>
> that means this should be done in a single patch.
Yes, please combine the patches. I can ack it then so it can be
routed through arm-soc.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2016-09-20 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 2:42 [PATCH 0/2] ARM: imx31/of: clk: init clock controller with CLK_OF_DECLARE Vladimir Zapolskiy
2016-09-19 2:42 ` [PATCH 1/2] ARM: imx31: remove mx31_clocks_init_dt() function calls Vladimir Zapolskiy
2016-09-19 2:42 ` [PATCH 2/2] clk: imx31: properly init clocks for machines with DT Vladimir Zapolskiy
2016-09-20 17:36 ` Stephen Boyd
2016-09-19 5:58 ` [PATCH 0/2] ARM: imx31/of: clk: init clock controller with CLK_OF_DECLARE Uwe Kleine-König
2016-09-20 17:32 ` Stephen Boyd [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=20160920173250.GB8319@codeaurora.org \
--to=sboyd@codeaurora.org \
--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).