From: Viresh Kumar <viresh.kumar@linaro.org>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: Shawn Guo <shawnguo@kernel.org>, Jacky Bai <ping.bai@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Dong Aisheng <aisheng.dong@nxp.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] Add imx7d speed grading and higher OPPs
Date: Thu, 6 Jun 2019 08:38:38 +0530 [thread overview]
Message-ID: <20190606030838.l45zjkdl6uycp75j@vireshk-i7> (raw)
In-Reply-To: <cover.1559730963.git.leonard.crestez@nxp.com>
On 05-06-19, 13:37, Leonard Crestez wrote:
> Changes since v1:
> * Remove the match list from imx-cpufreq-dt
> * Split arch and cpufreq changes
> Link to v1: https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=124427
>
> Leonard Crestez (5):
> cpufreq: imx-cpufreq-dt: Remove global platform match list
Added following to this patch:
Suggested-by: Viresh Kumar <viresh.kumar@linaro.org>
> cpufreq: Switch imx7d to imx-cpufreq-dt for speed grading
Applied the first two patches. Thanks.
--
viresh
next prev parent reply other threads:[~2019-06-06 3:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:37 [PATCH 0/5] Add imx7d speed grading and higher OPPs Leonard Crestez
2019-06-05 10:37 ` [PATCH v2 1/5] cpufreq: imx-cpufreq-dt: Remove global platform match list Leonard Crestez
2019-06-05 10:37 ` [PATCH v2 2/5] cpufreq: Switch imx7d to imx-cpufreq-dt for speed grading Leonard Crestez
2019-06-05 10:37 ` [PATCH v2 3/5] ARM: imx: Switch imx7d to imx-cpufreq-dt for speed-grading Leonard Crestez
2019-06-05 10:37 ` [PATCH v2 4/5] ARM: dts: imx7d: Update cpufreq OPP table Leonard Crestez
2019-06-05 10:37 ` [PATCH v2 5/5] ARM: imx_v6_v7_defconfig: Enable CONFIG_ARM_IMX_CPUFREQ_DT Leonard Crestez
2019-06-06 3:08 ` Viresh Kumar [this message]
2019-06-12 10:33 ` [PATCH 0/5] Add imx7d speed grading and higher OPPs 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=20190606030838.l45zjkdl6uycp75j@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=Anson.Huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=ping.bai@nxp.com \
--cc=rjw@rjwysocki.net \
--cc=shawnguo@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).