All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Amir Ayupov <aaupov@fb.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: drivers/hwtracing/coresight/coresight-cfg-pmu-pulse.c:51:27: sparse: sparse: incorrect type in initializer (different modifiers)
Date: Sun, 04 Oct 2026 13:22:31 +0200	[thread overview]
Message-ID: <202610041344.ILNmjSYE-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Amir-Ayupov/coresight-Add-pmu_pulse-extout_pulse/20260930-233744
head:   2906079546bf3a56f4104268fc0912c780570e93
commit: 2906079546bf3a56f4104268fc0912c780570e93 coresight: Add pmu_pulse/extout_pulse
date:   3 days ago
config: arm64-randconfig-r2305-20261004 (https://download.01.org/0day-ci/archive/20261004/202610041344.ILNmjSYE-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261004/202610041344.ILNmjSYE-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/202610041344.ILNmjSYE-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/hwtracing/coresight/coresight-cfg-pmu-pulse.c:51:27: sparse: sparse: incorrect type in initializer (different modifiers) @@     expected char const **feat_ref_names @@     got char const *const * @@
   drivers/hwtracing/coresight/coresight-cfg-pmu-pulse.c:51:27: sparse:     expected char const **feat_ref_names
   drivers/hwtracing/coresight/coresight-cfg-pmu-pulse.c:51:27: sparse:     got char const *const *

vim +51 drivers/hwtracing/coresight/coresight-cfg-pmu-pulse.c

    45	
    46	struct cscfg_config_desc pmu_pulse_etm4x = {
    47		.name = "pmu_pulse",
    48		.description = "Pulse ETM external output 1 on every traced cycle for the PMU\n"
    49		"to count as TRCEXTOUT1\n",
    50		.nr_feat_refs = ARRAY_SIZE(pmu_pulse_ref_names),
  > 51		.feat_ref_names = pmu_pulse_ref_names,
    52	};
    53	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-10-04 11:22 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=202610041344.ILNmjSYE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aaupov@fb.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.