All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Dinh Nguyen <dinguyen@kernel.org>
Subject: [dinguyen:socfpga_firmware_for_v7.1 2/2] drivers/firmware/stratix10-svc.c:271:33: error: array has incomplete element type 'struct stratix10_svc_chan'
Date: Fri, 20 Mar 2026 15:06:12 +0800	[thread overview]
Message-ID: <202603201536.KvAI7CLq-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git socfpga_firmware_for_v7.1
head:   6146df4b6330e6ec1a1273f77f817bc917548f69
commit: 6146df4b6330e6ec1a1273f77f817bc917548f69 [2/2] firmware: stratix10-svc: kmalloc_array + kzalloc to flex
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260320/202603201536.KvAI7CLq-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/20260320/202603201536.KvAI7CLq-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/202603201536.KvAI7CLq-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/firmware/stratix10-svc.c:271:33: error: array has incomplete element type 'struct stratix10_svc_chan'
     271 |         struct stratix10_svc_chan chans[] __counted_by(num_chans);
         |                                        ^
   include/linux/firmware/intel/stratix10-svc-client.h:78:8: note: forward declaration of 'struct stratix10_svc_chan'
      78 | struct stratix10_svc_chan;
         |        ^
   1 error generated.


vim +271 drivers/firmware/stratix10-svc.c

   242	
   243	/**
   244	 * struct stratix10_svc_controller - service controller
   245	 * @dev: device
   246	 * @num_chans: number of channels in 'chans' array
   247	 * @num_active_client: number of active service client
   248	 * @node: list management
   249	 * @genpool: memory pool pointing to the memory region
   250	 * @complete_status: state for completion
   251	 * @invoke_fn: function to issue secure monitor call or hypervisor call
   252	 * @svc: manages the list of client svc drivers
   253	 * @sdm_lock: only allows a single command single response to SDM
   254	 * @actrl: async control structure
   255	 * @chans: array of service channels
   256	 *
   257	 * This struct is used to create communication channels for service clients, to
   258	 * handle secure monitor or hypervisor call.
   259	 */
   260	struct stratix10_svc_controller {
   261		struct device *dev;
   262		int num_chans;
   263		int num_active_client;
   264		struct list_head node;
   265		struct gen_pool *genpool;
   266		struct completion complete_status;
   267		svc_invoke_fn *invoke_fn;
   268		struct stratix10_svc *svc;
   269		struct mutex sdm_lock;
   270		struct stratix10_async_ctrl actrl;
 > 271		struct stratix10_svc_chan chans[] __counted_by(num_chans);
   272	};
   273	

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

                 reply	other threads:[~2026-03-20  7: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=202603201536.KvAI7CLq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dinguyen@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rosenp@gmail.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.