From: Viresh Kumar <viresh.kumar@linaro.org>
To: sean.wang@mediatek.com
Cc: rjw@rjwysocki.net, robh+dt@kernel.org, matthias.bgg@gmail.com,
jdelvare@suse.de, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] cpufreq: mediatek: add cleanups with the more generic naming
Date: Wed, 9 Aug 2017 19:56:05 +0530 [thread overview]
Message-ID: <20170809142605.GC29383@vireshk-i7> (raw)
In-Reply-To: <c658e5aa68d26c645a8ecd58da69576c9fe237c5.1502272372.git.sean.wang@mediatek.com>
On 09-08-17, 18:12, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Since more MediaTek SoCs can be supported with the cpufreq driver and not
> limited to MT8173, a couple of cleanups are done here with renaming those
> functions and related structures with "mtk" instead of "mt8173".
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> ---
> drivers/cpufreq/mediatek-cpufreq.c | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2017-08-09 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 10:12 [PATCH 0/2] add cpufreq support to MT7622 sean.wang
2017-08-09 10:12 ` [PATCH 2/2] cpufreq: mediatek: add support of cpufreq to MT7622 SoC sean.wang
2017-08-09 14:26 ` Viresh Kumar
[not found] ` <cover.1502272372.git.sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-09 10:12 ` [PATCH 1/2] cpufreq: mediatek: add cleanups with the more generic naming sean.wang-NuS5LvNUpcJWk0Htik3J/w
2017-08-09 14:26 ` Viresh Kumar [this message]
2017-08-10 23:13 ` [PATCH 0/2] add cpufreq support to MT7622 Rafael J. Wysocki
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=20170809142605.GC29383@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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).