public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: sboyd@kernel.org, michael@amarulasolutions.com,
	stefan.wahren@i2se.com, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, anson.huang@nxp.com, stefan@agner.ch,
	Fabio Estevam <fabio.estevam@nxp.com>
Subject: Re: [PATCH v2] dt-bindings: clock: imx6ul: Do not change the clock definition order
Date: Tue, 5 Jun 2018 15:08:55 -0600	[thread overview]
Message-ID: <20180605210855.GA27408@rob-hp-laptop> (raw)
In-Reply-To: <1527948122-32092-1-git-send-email-festevam@gmail.com>

On Sat, Jun 02, 2018 at 11:02:02AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@nxp.com>
> 
> Commit f5a4670de966 ("clk: imx: Add new clo01 and clo2 controlled
> by CCOSR") introduced the CLK_CLKO definitions, but didn't put them
> at the end of the list, which may cause dtb breakage when running an old
> dtb with a newer kernel.
> 
> In order to avoid that, simply add the new CLK_CKO clock definitions
> at the end of the list.
> 
> Fixes: f5a4670de966 ("clk: imx: Add new clo01 and clo2 controlled by CCOSR")
> Reported-by: Stefan Wahren <stefan.wahren@i2se.com>
> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
> ---
> Changes since v1:
> - Use 12 char for the commit id
> 
>  include/dt-bindings/clock/imx6ul-clock.h | 40 +++++++++++++++-----------------
>  1 file changed, 19 insertions(+), 21 deletions(-)

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

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02 14:02 [PATCH v2] dt-bindings: clock: imx6ul: Do not change the clock definition order Fabio Estevam
2018-06-05 21:08 ` Rob Herring [this message]
2018-06-06 16:27 ` Stefan Agner
2018-06-06 21:56   ` Fabio Estevam
2018-06-29 18:26 ` 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=20180605210855.GA27408@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=anson.huang@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=michael@amarulasolutions.com \
    --cc=sboyd@kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=stefan@agner.ch \
    /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