From: Shawn Guo <shawnguo@kernel.org>
To: Abel Vesa <abel.vesa@nxp.com>
Cc: Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mike Turquette <mturquette@baylibre.com>,
Sascha Hauer <kernel@pengutronix.de>,
Lucas Stach <l.stach@pengutronix.de>,
Angus Ainslie <angus.ainslie@puri.sm>,
Anson Huang <anson.huang@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@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 v3 0/3] arm: dts: imx8mq: Add cpufreq support
Date: Mon, 4 Mar 2019 13:25:30 +0800 [thread overview]
Message-ID: <20190304052528.GW26041@dragon> (raw)
In-Reply-To: <1551390149-15443-1-git-send-email-abel.vesa@nxp.com>
On Thu, Feb 28, 2019 at 09:42:43PM +0000, Abel Vesa wrote:
> Changes since v2:
> * renamed the regulator
> * removed the useless enable-active-high from the regulator
> * renamed a53_0_opp_table to a53_opp_table
>
> Abel Vesa (3):
> arm64: dts: imx8mq: Add the clocks and the latencies for the A53 cores
> arm64: dts: imx8mq: Add the buck vdd_arm regulator
> arm64: dts: imx8mq: Add the opp table and cores opp properties
Applied all, thanks.
prev parent reply other threads:[~2019-03-04 5:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 21:42 [PATCH v3 0/3] arm: dts: imx8mq: Add cpufreq support Abel Vesa
2019-02-28 21:42 ` [PATCH v3 1/3] arm64: dts: imx8mq: Add the clocks and the latencies for the A53 cores Abel Vesa
2019-02-28 21:42 ` [PATCH v3 2/3] arm64: dts: imx8mq: Add the buck vdd_arm regulator Abel Vesa
2019-02-28 21:42 ` [PATCH v3 3/3] arm64: dts: imx8mq: Add the opp table and cores opp properties Abel Vesa
2019-03-04 5:25 ` 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=20190304052528.GW26041@dragon \
--to=shawnguo@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=angus.ainslie@puri.sm \
--cc=anson.huang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@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=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).