From: Shawn Guo <shawnguo@kernel.org>
To: Anson Huang <anson.huang@nxp.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"S.j. Wang" <shengjiu.wang@nxp.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
"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 2/2] ARM: dts: imx6sx-sabreauto: add external 24MHz clock source
Date: Thu, 19 Apr 2018 22:03:31 +0800 [thread overview]
Message-ID: <20180419140330.GV25429@dragon> (raw)
In-Reply-To: <AM3PR04MB1315FCBBAFCE808BD35FF2CFF5B50@AM3PR04MB1315.eurprd04.prod.outlook.com>
On Thu, Apr 19, 2018 at 03:23:39AM +0000, Anson Huang wrote:
> If so, I think we should use V1 patch to keep clocks container?
Ah, right. I will just pick up v1 of patch #2.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/2] ARM: dts: imx6sx-sabreauto: add external 24MHz clock source
Date: Thu, 19 Apr 2018 22:03:31 +0800 [thread overview]
Message-ID: <20180419140330.GV25429@dragon> (raw)
In-Reply-To: <AM3PR04MB1315FCBBAFCE808BD35FF2CFF5B50@AM3PR04MB1315.eurprd04.prod.outlook.com>
On Thu, Apr 19, 2018 at 03:23:39AM +0000, Anson Huang wrote:
> If so, I think we should use V1 patch to keep clocks container?
Ah, right. I will just pick up v1 of patch #2.
Shawn
next prev parent reply other threads:[~2018-04-19 14:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 2:30 [PATCH V2 1/2] clk: imx6sx: add missing lvds2 clock to the clock tree Anson Huang
2018-03-19 2:30 ` Anson Huang
2018-03-19 2:30 ` Anson Huang
2018-03-19 2:30 ` [PATCH V2 2/2] ARM: dts: imx6sx-sabreauto: add external 24MHz clock source Anson Huang
2018-03-19 2:30 ` Anson Huang
2018-03-19 2:30 ` Anson Huang
2018-04-17 14:22 ` Shawn Guo
2018-04-17 14:22 ` Shawn Guo
2018-04-19 3:17 ` Stephen Boyd
2018-04-19 3:17 ` Stephen Boyd
2018-04-19 3:17 ` Stephen Boyd
2018-04-19 3:23 ` Anson Huang
2018-04-19 3:23 ` Anson Huang
2018-04-19 3:23 ` Anson Huang
2018-04-19 14:03 ` Shawn Guo [this message]
2018-04-19 14:03 ` Shawn Guo
2018-04-19 14:02 ` Shawn Guo
2018-04-19 14:02 ` Shawn Guo
2018-04-19 14:24 ` Shawn Guo
2018-04-19 14:24 ` Shawn Guo
2018-04-19 19:32 ` Stephen Boyd
2018-04-19 19:32 ` Stephen Boyd
2018-04-19 19:32 ` Stephen Boyd
2018-03-26 22:23 ` [PATCH V2 1/2] clk: imx6sx: add missing lvds2 clock to the clock tree Rob Herring
2018-03-26 22:23 ` Rob Herring
2018-04-16 18:32 ` Stephen Boyd
2018-04-16 18:32 ` Stephen Boyd
2018-04-16 18:32 ` Stephen Boyd
2018-04-19 14:57 ` Shawn Guo
2018-04-19 14:57 ` Shawn Guo
2018-04-20 6:57 ` Anson Huang
2018-04-20 6:57 ` Anson Huang
2018-04-20 6:57 ` Anson Huang
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=20180419140330.GV25429@dragon \
--to=shawnguo@kernel.org \
--cc=anson.huang@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=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shengjiu.wang@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.