From: Viresh Kumar <viresh.kumar@linaro.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
linux-pm@vger.kernel.org, lkp@lists.01.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [cpufreq] a6cb305191: kernel_BUG_at_drivers/cpufreq/cpufreq.c
Date: Fri, 27 May 2022 09:24:42 +0530 [thread overview]
Message-ID: <20220527035442.su7hridojtvik5x7@vireshk-i7> (raw)
In-Reply-To: <20220527031320.GA10419@xsang-OptiPlex-9020>
On 27-05-22, 11:13, kernel test robot wrote:
> [ 10.349308][ T200] cpufreq_online (drivers/cpufreq/cpufreq.c:1562)
> [ 10.349314][ T200] cpufreq_add_dev (drivers/cpufreq/cpufreq.c:1578)
> [ 10.349318][ T200] subsys_interface_register (drivers/base/bus.c:1036)
Thanks. I have updated the patch now to fix this.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: lkp@lists.01.org
Subject: Re: [cpufreq] a6cb305191: kernel_BUG_at_drivers/cpufreq/cpufreq.c
Date: Fri, 27 May 2022 09:24:42 +0530 [thread overview]
Message-ID: <20220527035442.su7hridojtvik5x7@vireshk-i7> (raw)
In-Reply-To: <20220527031320.GA10419@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
On 27-05-22, 11:13, kernel test robot wrote:
> [ 10.349308][ T200] cpufreq_online (drivers/cpufreq/cpufreq.c:1562)
> [ 10.349314][ T200] cpufreq_add_dev (drivers/cpufreq/cpufreq.c:1578)
> [ 10.349318][ T200] subsys_interface_register (drivers/base/bus.c:1036)
Thanks. I have updated the patch now to fix this.
--
viresh
next prev parent reply other threads:[~2022-05-27 3:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 11:51 [PATCH 0/3] cpufreq: Minor cleanups Viresh Kumar
2022-05-26 11:51 ` [PATCH 1/3] cpufreq: Optimize cpufreq_show_cpus() Viresh Kumar
2022-05-26 11:51 ` [PATCH 2/3] cpufreq: Panic if policy is active in cpufreq_policy_free() Viresh Kumar
2022-05-27 3:13 ` [cpufreq] a6cb305191: kernel_BUG_at_drivers/cpufreq/cpufreq.c kernel test robot
2022-05-27 3:13 ` kernel test robot
2022-05-27 3:54 ` Viresh Kumar [this message]
2022-05-27 3:54 ` Viresh Kumar
2022-05-27 3:53 ` [PATCH V2 2/3] cpufreq: Panic if policy is active in cpufreq_policy_free() Viresh Kumar
2022-06-14 13:59 ` Rafael J. Wysocki
2022-06-15 4:59 ` Viresh Kumar
2022-07-06 13:49 ` Rafael J. Wysocki
2022-07-06 15:23 ` Viresh Kumar
2022-07-06 15:34 ` Rafael J. Wysocki
2022-05-26 11:51 ` [PATCH 3/3] cpufreq: Drop unnecessary cpus locking from store() Viresh Kumar
2022-06-14 13:51 ` Rafael J. Wysocki
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=20220527035442.su7hridojtvik5x7@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=rafael@kernel.org \
--cc=vincent.guittot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.