From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
open list <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Stephan Gerhold <stephan@gerhold.net>,
Rajendra Nayak <rnayak@codeaurora.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
sbhanu@codeaurora.org, Sibi Sankar <sibis@codeaurora.org>,
Matthias Kaehlcke <mka@chromium.org>,
Stephen Boyd <sboyd@kernel.org>,
nm@ti.com
Subject: Re: WARNING: at drivers/opp/core.c:678 dev_pm_opp_set_rate+0x4cc/0x5d4 - on arm x15
Date: Fri, 28 Aug 2020 15:42:47 +0530 [thread overview]
Message-ID: <CA+G9fYsn1S-SieuP85-Z4qKO+aNyqJarrBR0xx0X-YbtF9eo0g@mail.gmail.com> (raw)
In-Reply-To: <20200828045128.y7ybkd7dnvn4h6dt@vireshk-i7>
On Fri, 28 Aug 2020 at 10:21, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
> On 27-08-20, 21:18, Stephen Rothwell wrote:
> > Hi Viresh,
> >
> > On Thu, 27 Aug 2020 15:16:51 +0530 Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > >
> > > On 27-08-20, 15:04, Naresh Kamboju wrote:
> > > > While boot testing arm x15 devices the Kernel warning noticed with linux next
> > > > tag 20200825.
> > > >
> > > > BAD: next-20200825
> > > > GOOD: next-20200824
> > > >
> > > > We are working on git bisect and boot testing on x15 and get back to you.
Viresh,
I have applied the v2 patch series on top of linux next-20200824.
and tested again the reported kernel warning is fixed [1]
[1] https://lkft.validation.linaro.org/scheduler/job/1717615#L1881
next prev parent reply other threads:[~2020-08-28 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 9:34 WARNING: at drivers/opp/core.c:678 dev_pm_opp_set_rate+0x4cc/0x5d4 - on arm x15 Naresh Kamboju
2020-08-27 9:46 ` Viresh Kumar
2020-08-27 11:01 ` Naresh Kamboju
2020-08-27 11:18 ` Stephen Rothwell
2020-08-28 4:51 ` Viresh Kumar
2020-08-28 10:12 ` Naresh Kamboju [this message]
2020-08-31 4:41 ` Viresh Kumar
2020-08-31 6:00 ` Naresh Kamboju
2020-08-31 6:02 ` Viresh Kumar
2020-10-15 9:56 ` Naresh Kamboju
2020-10-16 5:45 ` Viresh Kumar
2020-10-20 10:36 ` 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=CA+G9fYsn1S-SieuP85-Z4qKO+aNyqJarrBR0xx0X-YbtF9eo0g@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=krzk@kernel.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=mka@chromium.org \
--cc=nm@ti.com \
--cc=rnayak@codeaurora.org \
--cc=sbhanu@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sibis@codeaurora.org \
--cc=stephan@gerhold.net \
--cc=ulf.hansson@linaro.org \
--cc=viresh.kumar@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;
as well as URLs for NNTP newsgroup(s).