From: Stephen Boyd <sboyd@kernel.org>
To: Abel Vesa <abel.vesa@nxp.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: fsl: scu: add imx8dxl scu clock support
Date: Fri, 25 Feb 2022 14:47:30 -0800 [thread overview]
Message-ID: <20220225224732.63E24C340E7@smtp.kernel.org> (raw)
In-Reply-To: <20220222082140.2073629-1-abel.vesa@nxp.com>
Quoting Abel Vesa (2022-02-22 00:21:40)
> Add imx8dxl scu clock support.
>
> Signed-off-by: Abel Vesa <abel.vesa@nxp.com>
> ---
Acked-by: Stephen Boyd <sboyd@kernel.org>
next prev parent reply other threads:[~2022-02-25 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 8:21 [PATCH] dt-bindings: fsl: scu: add imx8dxl scu clock support Abel Vesa
2022-02-25 19:16 ` Rob Herring
2022-02-28 9:24 ` Abel Vesa
2022-02-25 22:47 ` Stephen Boyd [this message]
2022-02-28 9:27 ` Abel Vesa
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=20220225224732.63E24C340E7@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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