linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: shawnguo@kernel.org, kernel@pengutronix.de,
	fabio.estevam@nxp.com, mark.rutland@arm.com,
	mturquette@baylibre.com, sboyd@kernel.org,
	michael@amarulasolutions.com, matteo.lisi@engicam.com,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	Linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] clk: imx6ul: add GPIO clock gates
Date: Tue, 5 Jun 2018 15:10:09 -0600	[thread overview]
Message-ID: <20180605211009.GA28373@rob-hp-laptop> (raw)
In-Reply-To: <1527990245-13619-1-git-send-email-Anson.Huang@nxp.com>

On Sun, Jun 03, 2018 at 09:44:04AM +0800, Anson Huang wrote:
> i.MX6UL has GPIO clock gates in CCM CCGR,
> add them into clock tree for clock management.
> 
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> changes since V1:
> 	Move IMX6UL_CLK_GPIOx definition to end of clock table;
> 	Based on Fabio's patch "[v2] dt-bindings: clock: imx6ul: Do not change the clock definition order".
>  drivers/clk/imx/clk-imx6ul.c             | 5 +++++
>  include/dt-bindings/clock/imx6ul-clock.h | 8 +++++++-
>  2 files changed, 12 insertions(+), 1 deletion(-)

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2018-06-05 21:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03  1:44 [PATCH V2 1/2] clk: imx6ul: add GPIO clock gates Anson Huang
2018-06-03  1:44 ` [PATCH V2 2/2] ARM: dts: imx6ul: add GPIO clocks Anson Huang
2018-06-03  2:06   ` Fabio Estevam
2018-06-03 20:57   ` Fabio Estevam
2018-06-25  3:14   ` Anson Huang
2018-06-28  0:52     ` Shawn Guo
2018-06-29 18:39       ` Stephen Boyd
2018-07-01  2:19         ` Shawn Guo
2018-07-06 17:15           ` Stephen Boyd
2018-07-11  8:28             ` Shawn Guo
2018-06-03  2:06 ` [PATCH V2 1/2] clk: imx6ul: add GPIO clock gates Fabio Estevam
2018-06-05 21:10 ` Rob Herring [this message]
2018-06-29 18:42 ` 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=20180605211009.GA28373@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=Anson.Huang@nxp.com \
    --cc=Linux-imx@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --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=matteo.lisi@engicam.com \
    --cc=michael@amarulasolutions.com \
    --cc=mturquette@baylibre.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).