From: kernel test robot <philip.li@intel.com>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Palmer Dabbelt" <palmer@rivosinc.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: drivers/cpufreq/cpufreq.c:475:17: sparse: sparse: incorrect type in assignment (different address spaces)
Date: Mon, 11 Dec 2023 17:03:24 +0800 [thread overview]
Message-ID: <ZXbQXCXVh8uK4JGc@rli9-mobl> (raw)
Hi Lad,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3b47bc037bd44f142ac09848e8d3ecccc726be99
commit: effae0e3d9e1139d583e9b5d050f4f948825b8a3 riscv: Kconfig: Enable cpufreq kconfig menu
date: 1 year ago
:::::: branch date: 26 hours ago
:::::: commit date: 1 year ago
config: riscv-randconfig-r031-20230608 (https://download.01.org/0day-ci/archive/20231201/202312010059.MQ446XMR-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20231201/202312010059.MQ446XMR-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202312010059.MQ446XMR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
WARNING: invalid argument to '-march': '_zicbom_zihintpause'
>> drivers/cpufreq/cpufreq.c:475:17: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct notifier_block *nb @@ got struct notifier_block [noderef] __rcu *static [addressable] [toplevel] head @@
drivers/cpufreq/cpufreq.c:475:17: sparse: expected struct notifier_block *nb
drivers/cpufreq/cpufreq.c:475:17: sparse: got struct notifier_block [noderef] __rcu *static [addressable] [toplevel] head
>> drivers/cpufreq/cpufreq.c:475:65: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected struct notifier_block *nb @@ got struct notifier_block [noderef] __rcu *next @@
drivers/cpufreq/cpufreq.c:475:65: sparse: expected struct notifier_block *nb
drivers/cpufreq/cpufreq.c:475:65: sparse: got struct notifier_block [noderef] __rcu *next
vim +475 drivers/cpufreq/cpufreq.c
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 466
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 467 static void cpufreq_list_transition_notifiers(void)
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 468 {
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 469 struct notifier_block *nb;
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 470
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 471 pr_info("Registered transition notifiers:\n");
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 472
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 473 mutex_lock(&cpufreq_transition_notifier_list.mutex);
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 474
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 @475 for (nb = cpufreq_transition_notifier_list.head; nb; nb = nb->next)
d75f773c86a2b8 Sakari Ailus 2019-03-25 476 pr_info("%pS\n", nb->notifier_call);
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 477
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 478 mutex_unlock(&cpufreq_transition_notifier_list.mutex);
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 479 }
b7898fda5bc7e7 Rafael J. Wysocki 2016-03-30 480
:::::: The code at line 475 was first introduced by commit
:::::: b7898fda5bc7e786e76ce24fbd2ec993b08ec518 cpufreq: Support for fast frequency switching
:::::: TO: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
:::::: CC: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-11 9:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZXbQXCXVh8uK4JGc@rli9-mobl \
--to=philip.li@intel.com \
--cc=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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
all inboxes | Powered by JetHome®