From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Rob Herring <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Hector Yuan <hector.yuan@mediatek.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains
Date: Mon, 24 May 2021 14:47:15 +0530 [thread overview]
Message-ID: <20210524091715.wb6c4m3sicbypkaa@vireshk-i7> (raw)
In-Reply-To: <20210521152431.wspnsji3z7pmmdlf@bogus>
On 21-05-21, 16:24, Sudeep Holla wrote:
> On Fri, May 21, 2021 at 09:38:34AM +0530, Viresh Kumar wrote:
> > On 20-05-21, 14:43, Rob Herring wrote:
> > > Not allowed because I can't turn this check on by default until we get
> > > rid of the existing 80 or so. But it is a new check and Viresh already
> > > applied, so oh well.
> >
> > I can always drop it :)
> >
>
> While I really don't care(evident by rate at which I worked on this 😉)
> I think Hector Yuan won't be happy to wait I guess. As a quick fix, you
> can update "qcom,cpufreq-hw" to "mediatek,cpufreq-hw". You will still
> get warning with this patch + update alone, but once you have Hector's
> mediatek cpufreq driver applied, the warnings must disappear.
>
> What do you think ?
I guess you can send a fix later then.
--
viresh
next prev parent reply other threads:[~2021-05-24 9:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:54 [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains Sudeep Holla
2021-05-17 19:17 ` Rob Herring
2021-05-19 11:23 ` Sudeep Holla
2021-05-20 3:54 ` Viresh Kumar
2021-05-17 20:45 ` Rob Herring
2021-05-19 11:20 ` Sudeep Holla
2021-05-20 19:43 ` Rob Herring
2021-05-21 4:08 ` Viresh Kumar
2021-05-21 15:24 ` Sudeep Holla
2021-05-24 9:17 ` Viresh Kumar [this message]
2021-05-24 10:05 ` Sudeep Holla
2021-10-14 10:56 ` Ulf Hansson
2021-10-14 14:55 ` Sudeep Holla
2021-10-15 9:17 ` Ulf Hansson
2021-10-19 7:24 ` Viresh Kumar
2021-10-19 13:58 ` Ulf Hansson
2021-10-20 6:24 ` Viresh Kumar
2021-10-20 10:25 ` Sudeep Holla
2021-10-21 13:34 ` Ulf Hansson
2021-10-21 15:35 ` Sudeep Holla
2021-10-20 12:11 ` Rob Herring
2021-10-21 13:13 ` Ulf Hansson
2021-10-21 13:33 ` Sudeep Holla
2021-10-21 16:01 ` Ulf Hansson
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=20210524091715.wb6c4m3sicbypkaa@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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).