From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sascha Hauer <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
dl-linux-imx <linux-imx@nxp.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-clk <linux-clk@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH V3 0/5] imx esdhc dt/driver update
Date: Mon, 8 Mar 2021 08:51:45 +0800 [thread overview]
Message-ID: <20210308005144.GN543@dragon> (raw)
In-Reply-To: <DB6PR0402MB276016438D7D39579A05D08A88989@DB6PR0402MB2760.eurprd04.prod.outlook.com>
On Wed, Mar 03, 2021 at 03:00:57AM +0000, Peng Fan (OSS) wrote:
> Hi Shawn,
>
> > Subject: Re: [PATCH V3 0/5] imx esdhc dt/driver update
> >
> > On Thu, 25 Feb 2021 at 04:22, <peng.fan@oss.nxp.com> wrote:
> > >
> > > From: Peng Fan <peng.fan@nxp.com>
> > >
> > > V3:
> > > Patch 1, drop unneeded pinctrl-0/1/2
> > > Patch 2 is new to avoid break dt bindings check
> > > V2:
> > > patch 1, 2, 3 is new
> > > patch 4 is not changed
> > >
> > >
> > > Peng Fan (5):
> > > dt-bindings: mmc: fsl-imx-esdhc: add pinctrl bindings
> > > dt-bindings: clock: imx8qxp-lpcg: correct the example clock-names
> > > arm64: dts: imx8qxp: correct usdhc clock-names sequence
> > > dt-bindings: mmc: fsl-imx-esdhc: add clock bindings
> > > mmc: sdhci-esdhc-imx: validate pinctrl before use it
> > >
> > > .../bindings/clock/imx8qxp-lpcg.yaml | 6 +++---
> > > .../bindings/mmc/fsl-imx-esdhc.yaml | 20
> > +++++++++++++++++++
> > > arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 18 ++++++++---------
> > > drivers/mmc/host/sdhci-esdhc-imx.c | 2 +-
> > > 4 files changed, 33 insertions(+), 13 deletions(-)
> > >
> > > --
> > > 2.30.0
> > >
> >
> > Applied patch 1, 4 and 5, thanks!
>
>
> Would you pick patch 2,3?
Done.
prev parent reply other threads:[~2021-03-08 0:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 3:09 [PATCH V3 0/5] imx esdhc dt/driver update peng.fan
2021-02-25 3:10 ` [PATCH V3 1/5] dt-bindings: mmc: fsl-imx-esdhc: add pinctrl bindings peng.fan
2021-02-25 3:10 ` [PATCH V3 2/5] dt-bindings: clock: imx8qxp-lpcg: correct the example clock-names peng.fan
2021-03-06 20:39 ` Rob Herring
2021-02-25 3:10 ` [PATCH V3 3/5] arm64: dts: imx8qxp: correct usdhc clock-names sequence peng.fan
2021-02-25 3:10 ` [PATCH V3 4/5] dt-bindings: mmc: fsl-imx-esdhc: add clock bindings peng.fan
2021-03-04 22:48 ` Rob Herring
2021-03-05 0:38 ` Peng Fan
2021-03-05 14:09 ` Aisheng Dong
2021-03-05 14:14 ` Rob Herring
2021-03-06 4:53 ` Aisheng Dong
2021-02-25 3:10 ` [PATCH V3 5/5] mmc: sdhci-esdhc-imx: validate pinctrl before use it peng.fan
2021-03-02 10:39 ` [PATCH V3 0/5] imx esdhc dt/driver update Ulf Hansson
2021-03-03 3:00 ` Peng Fan (OSS)
2021-03-08 0:51 ` Shawn Guo [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=20210308005144.GN543@dragon \
--to=shawnguo@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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-mmc@vger.kernel.org \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.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).