From: Abel Vesa <abel.vesa@nxp.com>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: Aisheng Dong <aisheng.dong@nxp.com>, Jacky Bai <ping.bai@nxp.com>,
Anson Huang <anson.huang@nxp.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] clk: imx8m: Add GIC clock
Date: Wed, 22 May 2019 10:56:28 +0000 [thread overview]
Message-ID: <20190522105627.nshnk5ih6r2swzr4@fsr-ub1664-175> (raw)
In-Reply-To: <cover.1558518323.git.leonard.crestez@nxp.com>
On 19-05-22 09:48:28, Leonard Crestez wrote:
> Add gic clk and mark it as critical so that parents are not turned off
> by accident.
>
> Changes since v1:
> * Add imx8mq
> * Split dt-bindings to separate patch
> * Rebase on shawnguo/clk/imx
> Link to v1: https://patchwork.kernel.org/patch/10940303/
>
For the entire series.
Reviewed-by: Abel Vesa <abel.vesa@nxp.com>
> Leonard Crestez (2):
> dt-bindings: clock: imx8m: Add GIC clock
> clk: imx8m: Add GIC clock
>
> drivers/clk/imx/clk-imx8mm.c | 4 ++++
> drivers/clk/imx/clk-imx8mq.c | 4 ++++
> include/dt-bindings/clock/imx8mm-clock.h | 4 +++-
> include/dt-bindings/clock/imx8mq-clock.h | 4 +++-
> 4 files changed, 14 insertions(+), 2 deletions(-)
>
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-22 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 9:48 [PATCH v2 0/2] clk: imx8m: Add GIC clock Leonard Crestez
2019-05-22 9:48 ` [PATCH v2 1/2] dt-bindings: clock: " Leonard Crestez
2019-05-22 9:48 ` [PATCH v2 2/2] clk: " Leonard Crestez
2019-05-22 10:56 ` Abel Vesa [this message]
2019-05-23 13:12 ` [PATCH v2 0/2] " Shawn Guo
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=20190522105627.nshnk5ih6r2swzr4@fsr-ub1664-175 \
--to=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@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).