From: Stephen Boyd <sboyd@kernel.org>
To: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>,
Stephen Boyd <sboyd@codeaurora.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [PATCH V3 5/5] clk: imx: scu: add fallback compatible string support
Date: Wed, 20 Feb 2019 12:57:15 -0800 [thread overview]
Message-ID: <155069623505.77512.17191789640283789974@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <AM6PR04MB42151CA6852C4EEA0FECC93C807D0@AM6PR04MB4215.eurprd04.prod.outlook.com>
Quoting Aisheng Dong (2019-02-19 23:09:57)
> Hi Stephen,
>
> Can you help picked this one?
> SCU clock is likely to be common, so we add a common
> compatible string to handle it.
>
> BTW Patch 1~2 already picked up by Shawn.
> Patch 3~4 dropped.
>
Sure. Picked into clk-next.
prev parent reply other threads:[~2019-02-20 20:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 13:22 [PATCH V3 0/5] dt-binding: clk: prepare for imx8qm clock support Aisheng Dong
2019-01-24 13:22 ` [PATCH V3 1/5] dt-bindings: fsl: scu: add fallback compatible string for clock Aisheng Dong
2019-02-01 6:21 ` Shawn Guo
2019-01-24 13:22 ` [PATCH V3 2/5] dt-bindings: fsl: scu: add imx8qm scu clock support Aisheng Dong
2019-02-01 6:22 ` Shawn Guo
2019-01-24 13:22 ` [PATCH V3 3/5] dt-bindings: clock: update CPU clock ID name Aisheng Dong
2019-01-24 13:22 ` [PATCH V3 4/5] dt-bindings: imx8-clock: add a53 and a72 clock id Aisheng Dong
2019-02-13 22:18 ` Rob Herring
2019-02-20 7:07 ` Aisheng Dong
2019-02-20 20:56 ` Stephen Boyd
2019-01-24 13:22 ` [PATCH V3 5/5] clk: imx: scu: add fallback compatible string support Aisheng Dong
2019-02-20 7:09 ` Aisheng Dong
2019-02-20 20:57 ` 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=155069623505.77512.17191789640283789974@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=aisheng.dong@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-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).