Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zhanjun Dong <zhanjun.dong@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Matt Roper <matthew.d.roper@intel.com>,
	Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: drivers/gpu/drm/xe/xe_guc_capture.c:218: warning: cannot understand function prototype: 'struct __guc_mmio_reg_descr_group *extlists; '
Date: Sun, 27 Apr 2025 00:17:57 +0800	[thread overview]
Message-ID: <202504270013.yxJGp0R1-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   02ddfb981de88a2c15621115dd7be2431252c568
commit: b170d696c1e2226713471d810c63b1162335079f drm/xe/guc: Add XE_LP steered register lists
date:   7 months ago
config: riscv-randconfig-002-20250426 (https://download.01.org/0day-ci/archive/20250427/202504270013.yxJGp0R1-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250427/202504270013.yxJGp0R1-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/202504270013.yxJGp0R1-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/xe/xe_guc_capture.c:218: warning: cannot understand function prototype: 'struct __guc_mmio_reg_descr_group *extlists; '


vim +218 drivers/gpu/drm/xe/xe_guc_capture.c

   211	
   212	struct xe_guc_state_capture {
   213		const struct __guc_mmio_reg_descr_group *reglists;
   214		/**
   215		 * NOTE: steered registers have multiple instances depending on the HW configuration
   216		 * (slices or dual-sub-slices) and thus depends on HW fuses discovered
   217		 */
 > 218		struct __guc_mmio_reg_descr_group *extlists;
   219		struct __guc_capture_ads_cache ads_cache[GUC_CAPTURE_LIST_INDEX_MAX]
   220							[GUC_STATE_CAPTURE_TYPE_MAX]
   221							[GUC_CAPTURE_LIST_CLASS_MAX];
   222		void *ads_null_cache;
   223	};
   224	

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

                 reply	other threads:[~2025-04-26 16:18 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=202504270013.yxJGp0R1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=matthew.d.roper@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=zhanjun.dong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox