From: Shawn Guo <shawnguo@kernel•org>
To: Anson Huang <anson.huang@nxp•com>
Cc: "mark.rutland@arm•com" <mark.rutland@arm•com>,
Aisheng Dong <aisheng.dong@nxp•com>,
"ulf.hansson@linaro•org" <ulf.hansson@linaro•org>,
"linux-watchdog@vger•kernel.org" <linux-watchdog@vger•kernel.org>,
"devicetree@vger•kernel.org" <devicetree@vger•kernel.org>,
Daniel Baluta <daniel.baluta@nxp•com>,
"s.hauer@pengutronix•de" <s.hauer@pengutronix•de>,
Peng Fan <peng.fan@nxp•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"robh+dt@kernel•org" <robh+dt@kernel•org>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
"kernel@pengutronix•de" <kernel@pengutronix•de>,
"wim@linux-watchdog•org" <wim@linux-watchdog•org>,
"festevam@gmail•com" <festevam@gmail•com>,
"linux@roeck-us•net" <linux@roeck-us•net>,
dl-linux-imx <linux-imx@nxp•com>
Subject: Re: [PATCH RESEND V4 2/3] arm64: dts: imx8qxp: Move watchdog node into scu node
Date: Wed, 5 Jun 2019 14:12:40 +0800 [thread overview]
Message-ID: <20190605061238.GC29853@dragon> (raw)
In-Reply-To: <DB3PR0402MB39161D679A11B05ADCA8A28BF5160@DB3PR0402MB3916.eurprd04.prod.outlook.com>
On Wed, Jun 05, 2019 at 06:09:12AM +0000, Anson Huang wrote:
> Hi, Shawn
>
> > -----Original Message-----
> > From: Shawn Guo <shawnguo@kernel•org>
> > Sent: Wednesday, June 5, 2019 2:00 PM
> > To: Anson Huang <anson.huang@nxp•com>
> > Cc: robh+dt@kernel•org; mark.rutland@arm•com; wim@linux-watchdog•org;
> > linux@roeck-us•net; s.hauer@pengutronix•de; kernel@pengutronix•de;
> > festevam@gmail•com; Aisheng Dong <aisheng.dong@nxp•com>;
> > ulf.hansson@linaro•org; Daniel Baluta <daniel.baluta@nxp•com>; Peng Fan
> > <peng.fan@nxp•com>; devicetree@vger•kernel.org; linux-
> > kernel@vger•kernel.org; linux-watchdog@vger•kernel.org; linux-arm-
> > kernel@lists•infradead.org; dl-linux-imx <linux-imx@nxp•com>
> > Subject: Re: [PATCH RESEND V4 2/3] arm64: dts: imx8qxp: Move watchdog
> > node into scu node
> >
> > On Tue, Jun 04, 2019 at 09:06:28AM +0000, Anson Huang wrote:
> > > Hi, Shawn
> > > The driver and binding doc are already reviewed and waiting for DT
> > patch, will you help review this DT patch?
> >
> > I'm fine with it. Should I just pick this patch up, or is there any dependency
> > we need to handle?
>
> No dependency, it just makes more sense to move the node into SCU node as it is NOW depending on SCU
> driver. Once you pick up this patch
Just applied.
> (and maybe the dt-binding patch as well?),
It makes more sense to have it go through watchdog tree.
Shawn
> I will notify the watchdog
> maintainer to pick up the watchdog patch in this series.
_______________________________________________
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-06-05 6:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 10:10 [PATCH RESEND V4 1/3] dt-bindings: watchdog: move i.MX system controller watchdog binding to SCU Anson Huang
2019-05-12 10:10 ` [PATCH RESEND V4 2/3] arm64: dts: imx8qxp: Move watchdog node into scu node Anson Huang
2019-06-04 9:06 ` Anson Huang
2019-06-05 6:00 ` Shawn Guo
2019-06-05 6:09 ` Anson Huang
2019-06-05 6:12 ` Shawn Guo [this message]
2019-05-12 10:10 ` [PATCH RESEND V4 3/3] watchdog: imx_sc: Add pretimeout support Anson Huang
2019-05-12 13:28 ` Guenter Roeck
2019-05-12 14:10 ` Anson Huang
2019-06-05 6:24 ` Anson Huang
2019-06-07 17:40 ` Guenter Roeck
2019-06-08 9:32 ` Anson Huang
2019-06-08 13:22 ` Guenter Roeck
2019-05-13 17:12 ` [PATCH RESEND V4 1/3] dt-bindings: watchdog: move i.MX system controller watchdog binding to SCU Rob Herring
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=20190605061238.GC29853@dragon \
--to=shawnguo@kernel$(echo .)org \
--cc=aisheng.dong@nxp$(echo .)com \
--cc=anson.huang@nxp$(echo .)com \
--cc=daniel.baluta@nxp$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=festevam@gmail$(echo .)com \
--cc=kernel@pengutronix$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-imx@nxp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-watchdog@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=mark.rutland@arm$(echo .)com \
--cc=peng.fan@nxp$(echo .)com \
--cc=robh+dt@kernel$(echo .)org \
--cc=s.hauer@pengutronix$(echo .)de \
--cc=ulf.hansson@linaro$(echo .)org \
--cc=wim@linux-watchdog$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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