[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190207040805.og4t2s5ycuy6hqab@vireshk-i7>
Date: Thu, 7 Feb 2019 09:38:05 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Quentin Perret <quentin.perret@....com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
Taniya Das <tdas@...eaurora.org>, CK Hu <ck.hu@...iatek.com>,
Eddie Huang <eddie.huang@...iatek.com>,
Nicolas Boichat <drinkcat@...omium.org>,
Douglas Anderson <dianders@...omium.org>
Subject: Re: [PATCH 2/2] cpufreq: mediatek: Register an Energy Model
On 06-02-19, 10:16, Matthias Kaehlcke wrote:
> You are prefectly right, I missed the obvious and didn't get my hands
> on hardware yet for testing.
>
> So much for screwing up a one-liner ... I'll send a fix.
>
> I thought Viresh already applied the patch, however in opp/linux-next
> I currently only see the other one of this series for qcom-hw, so it
> seems sending a new version rather than a fix-up patch is the way to
> go.
Yeah, I dropped it after Quentin reported the issue.
--
viresh
Powered by blists - more mailing lists