From: Abel Vesa <abel.vesa@linaro.org>
To: Wei Fang <wei.fang@nxp.com>
Cc: "mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"abelvesa@kernel.org" <abelvesa@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 RESEND 1/4] dt-bindings: clock: add i.MX95 NETCMIX block control
Date: Thu, 29 Aug 2024 09:50:09 +0300 [thread overview]
Message-ID: <ZtAaIRQqC15QPoMQ@linaro.org> (raw)
In-Reply-To: <PAXPR04MB8510AE921AD67C110F135BB988952@PAXPR04MB8510.eurprd04.prod.outlook.com>
On 24-08-28 09:31:08, Wei Fang wrote:
> > On 24-07-29 09:27:53, Wei Fang wrote:
> > > Add 'nxp,imx95-netcmix-blk-ctrl' compatible string for i.MX95 platform.
> > >
> > > Signed-off-by: Wei Fang <wei.fang@nxp.com>
> > > Acked-by: Rob Herring (Arm) <robh@kernel.org>
> > > ---
> > > Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> > b/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> > > index 2dffc02dcd8b..b0072bae12d9 100644
> > > --- a/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> > > +++ b/Documentation/devicetree/bindings/clock/nxp,imx95-blk-ctl.yaml
> > > @@ -17,6 +17,7 @@ properties:
> > > - nxp,imx95-display-csr
> > > - nxp,imx95-camera-csr
> > > - nxp,imx95-vpu-csr
> > > + - nxp,imx95-netcmix-blk-ctrl
> >
> > Move this above vpu-csr, please.
> >
> > Also, for some reason, this patchset doesn't apply cleanly.
> >
> > Please respin.
> >
>
> Okay, let me update my local tree. I use the linux-next tree as the code
> Base, is this tree okay?
Sure.
next prev parent reply other threads:[~2024-08-29 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 1:27 [PATCH v2 RESEND 0/4] add NETCMIX block control support on i.MX95 Wei Fang
2024-07-29 1:27 ` [PATCH v2 RESEND 1/4] dt-bindings: clock: add i.MX95 NETCMIX block control Wei Fang
2024-08-28 8:45 ` Abel Vesa
2024-08-28 9:31 ` Wei Fang
2024-08-29 6:50 ` Abel Vesa [this message]
2024-07-29 1:27 ` [PATCH v2 RESEND 2/4] dt-bindings: clock: add RMII clock selection Wei Fang
2024-07-29 1:27 ` [PATCH v2 RESEND 3/4] clk: imx95: enable the clock of NETCMIX block control Wei Fang
2024-07-29 1:27 ` [PATCH v2 RESEND 4/4] arm64: dts: imx95: Add NETCMIX block control support Wei Fang
2024-08-12 6:39 ` [PATCH v2 RESEND 0/4] add NETCMIX block control support on i.MX95 Wei Fang
2024-08-13 2:33 ` Shawn Guo
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=ZtAaIRQqC15QPoMQ@linaro.org \
--to=abel.vesa@linaro.org \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=wei.fang@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 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).