All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Will Deacon <will@kernel.org>,
	James Clark <james.clark@linaro.org>,
	Ilkka Koskinen <ilkka@os.amperecomputing.com>
Subject: [arm-perf:for-next/perf 14/15] drivers/perf/arm_cspmu/nvidia_cspmu.c:192:2: error: call to undeclared function 'writel'; ISO C99 and later do not support implicit function declarations
Date: Sat, 15 Mar 2025 07:05:27 +0800	[thread overview]
Message-ID: <202503150649.Dol8RBSh-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git for-next/perf
head:   a28f3cbfd11fcb13f826b33a4799c2ac77e70729
commit: 6de0298a3925f1e6e313430c45ae314a93f89ef6 [14/15] perf/arm_cspmu: Generalise event filtering
config: x86_64-buildonly-randconfig-002-20250315 (https://download.01.org/0day-ci/archive/20250315/202503150649.Dol8RBSh-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250315/202503150649.Dol8RBSh-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/202503150649.Dol8RBSh-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/perf/arm_cspmu/nvidia_cspmu.c:192:2: error: call to undeclared function 'writel'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     192 |         writel(filter, cspmu->base0 + offset);
         |         ^
   drivers/perf/arm_cspmu/nvidia_cspmu.c:200:2: error: call to undeclared function 'writel'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     200 |         writel(filter, cspmu->base0 + PMCCFILTR);
         |         ^
   2 errors generated.


vim +/writel +192 drivers/perf/arm_cspmu/nvidia_cspmu.c

   185	
   186	static void nv_cspmu_set_ev_filter(struct arm_cspmu *cspmu,
   187					   const struct perf_event *event)
   188	{
   189		u32 filter = nv_cspmu_event_filter(event);
   190		u32 offset = PMEVFILTR + (4 * event->hw.idx);
   191	
 > 192		writel(filter, cspmu->base0 + offset);
   193	}
   194	

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

                 reply	other threads:[~2025-03-14 23:06 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=202503150649.Dol8RBSh-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ilkka@os.amperecomputing.com \
    --cc=james.clark@linaro.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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.