From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Mansur Alisha Shaik <mansur@codeaurora.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
regressions@lists.linux.dev, Linux PM <linux-pm@vger.kernel.org>,
lkft-triage@lists.linaro.org, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
Abhinav Kumar <quic_abhinavk@quicinc.com>
Subject: Re: WARNING: CPU: 4 PID: 326 at drivers/opp/core.c:2471 dev_pm_opp_set_config+0x344/0x620
Date: Mon, 25 Jul 2022 17:39:49 +0530 [thread overview]
Message-ID: <20220725120949.fofc7chlsnrgfpvm@vireshk-i7> (raw)
In-Reply-To: <f914f5c5-dd61-8495-b362-3043406582da@linaro.org>
On 25-07-22, 14:55, Stanimir Varbanov wrote:
> Hi Viresh,
>
> I can take a look and provide a patch to fix that.
>
> But, is this a new warn or it is a consequence of new changes in
> opp/core.c ?
This WARN was missing earlier (by mistake) and is added now after some
redesigning. You can reproduce it on the OPP tree:
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git opp/linux-next
--
viresh
next prev parent reply other threads:[~2022-07-25 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 5:31 WARNING: CPU: 4 PID: 326 at drivers/opp/core.c:2471 dev_pm_opp_set_config+0x344/0x620 Naresh Kamboju
2022-07-25 10:27 ` Viresh Kumar
2022-07-25 11:55 ` Stanimir Varbanov
2022-07-25 12:09 ` Viresh Kumar [this message]
2022-08-01 2:36 ` Viresh Kumar
2022-08-01 7:38 ` Stanimir Varbanov
2022-08-01 11:36 ` Stanimir Varbanov
2022-08-01 11:43 ` 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=20220725120949.fofc7chlsnrgfpvm@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mansur@codeaurora.org \
--cc=naresh.kamboju@linaro.org \
--cc=nm@ti.com \
--cc=quic_abhinavk@quicinc.com \
--cc=regressions@lists.linux.dev \
--cc=sboyd@kernel.org \
--cc=stanimir.varbanov@linaro.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