From: Hector Yuan <hector.yuan@mediatek.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: <linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
<linux-kernel@vger.kernel.org>, <wsd_upstream@mediatek.com>
Subject: Re: [PATCH v1 1/1] cpufreq: mediatek-hw: Register EM power table
Date: Fri, 9 Oct 2020 12:42:59 +0800 [thread overview]
Message-ID: <1602218579.21446.57.camel@mtkswgap22> (raw)
In-Reply-To: <20201009041912.nzhvubzmfox2twxg@vireshk-i7>
On Fri, 2020-10-09 at 09:49 +0530, Viresh Kumar wrote:
> On 08-10-20, 20:13, Hector Yuan wrote:
> > From: "Hector.Yuan" <hector.yuan@mediatek.com>
> >
> > Register CPU power table to energy model framework
> >
> > Signed-off-by: Hector.Yuan <hector.yuan@mediatek.com>
> > ---
> > drivers/cpufreq/mediatek-cpufreq-hw.c | 50 +++++++++++++++++++++++++--------
> > 1 file changed, 38 insertions(+), 12 deletions(-)
>
> I don't see this file in mainline. What am I missing ?
>
Hi, Viresh:
Yes, I base on my patches which is currently reviewed by Rob for the
Device tree part.
As I mentioned in cover letter.
This patch depends on Mediatek cpufreq HW driver patch submitted by
Hector Yuan.
https://lkml.org/lkml/2020/9/10/13
I have asked your approval for sending my new patches based on it and
you said it's okay to you.
I will stop sending new patches if you have any concerns.
Thank you so much.
next prev parent reply other threads:[~2020-10-09 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 12:13 [PATCH v1] cpufreq: mediatek-hw: Register EM power table Hector Yuan
2020-10-08 12:13 ` [PATCH v1 1/1] " Hector Yuan
2020-10-08 12:55 ` Lukasz Luba
2020-10-09 4:31 ` Hector Yuan
2020-10-09 4:19 ` Viresh Kumar
2020-10-09 4:42 ` Hector Yuan [this message]
2020-10-09 5:15 ` Viresh Kumar
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=1602218579.21446.57.camel@mtkswgap22 \
--to=hector.yuan@mediatek.com \
--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=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=wsd_upstream@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).