From: kernel test robot <lkp@intel.com>
To: Zide Chen <zide.chen@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: arch/x86/events/intel/uncore_snb.c:596:14: error: incompatible function pointer types initializing 'int (*)(struct intel_uncore_box *)' with an expression of type 'void (struct intel_uncore_box *)'
Date: Fri, 15 May 2026 18:46:40 +0200 [thread overview]
Message-ID: <202605151809.IdCavpnO-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Zide-Chen/perf-x86-intel-uncore-Rename-refcount-fields-and-other-cleanups/20260515-133040
head: c085f636ae022b2ae8e592275c3c8547a660c069
commit: bafd0d397ee00033633fc9a8383d5726a36d72ba perf/x86/intel/uncore: Let init_box() callback report failures
date: 11 hours ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260515/202605151809.IdCavpnO-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260515/202605151809.IdCavpnO-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/oe-kbuild-all/202605151809.IdCavpnO-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/events/intel/uncore_snb.c:596:14: error: incompatible function pointer types initializing 'int (*)(struct intel_uncore_box *)' with an expression of type 'void (struct intel_uncore_box *)' [-Wincompatible-function-pointer-types]
596 | .init_box = adl_uncore_msr_init_box,
| ^~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +596 arch/x86/events/intel/uncore_snb.c
772ed05f3c5ce7 Kan Liang 2021-04-12 594
772ed05f3c5ce7 Kan Liang 2021-04-12 595 static struct intel_uncore_ops adl_uncore_msr_ops = {
772ed05f3c5ce7 Kan Liang 2021-04-12 @596 .init_box = adl_uncore_msr_init_box,
772ed05f3c5ce7 Kan Liang 2021-04-12 597 .enable_box = adl_uncore_msr_enable_box,
772ed05f3c5ce7 Kan Liang 2021-04-12 598 .disable_box = adl_uncore_msr_disable_box,
772ed05f3c5ce7 Kan Liang 2021-04-12 599 .exit_box = adl_uncore_msr_exit_box,
772ed05f3c5ce7 Kan Liang 2021-04-12 600 .disable_event = snb_uncore_msr_disable_event,
772ed05f3c5ce7 Kan Liang 2021-04-12 601 .enable_event = snb_uncore_msr_enable_event,
772ed05f3c5ce7 Kan Liang 2021-04-12 602 .read_counter = uncore_msr_read_counter,
772ed05f3c5ce7 Kan Liang 2021-04-12 603 };
772ed05f3c5ce7 Kan Liang 2021-04-12 604
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-15 16:47 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=202605151809.IdCavpnO-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zide.chen@intel.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 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.