Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nicolas Schier <nsc@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Sasha Levin" <sashal@kernel.org>,
	llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	"Harald Freudenberger" <freude@linux.ibm.com>,
	"Holger Dengler" <dengler@linux.ibm.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	"Huacai Chen" <chenhuacai@kernel.org>,
	"WANG Xuerui" <kernel@xen0n.name>,
	"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
	linux-kbuild@vger.kernel.org, linux-s390@vger.kernel.org,
	loongarch@lists.linux.dev, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"kernelci.org bot" <bot@kernelci.org>
Subject: Re: [PATCH] Move struct cpu_feature to a <linux/device-id/cpu_feature.h>
Date: Sat, 21 Nov 2026 13:51:44 +0100	[thread overview]
Message-ID: <awGT4AhwcFcLsW0c@levanger> (raw)
In-Reply-To: <202611211941.G0rlpNpN-lkp@intel.com>

On Sat, Nov 21, 2026 at 08:01:20PM +0800, kernel test robot wrote:
> Hi Nicolas,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on kvm/queue]
> [also build test ERROR on kvm/next linus/master v7.4-rc3]
> [cannot apply to kvm/linux-next next-20261119]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Nicolas-Schier/Move-struct-cpu_feature-to-a-linux-device-id-cpu_feature-h/20261120-212711
> base:   https://git.kernel.org/pub/scm/virt/kvm/kvm.git queue
> patch link:    https://lore.kernel.org/r/20261120202712.3377691-1-nsc%40kernel.org
> patch subject: [PATCH] Move struct cpu_feature to a <linux/device-id/cpu_feature.h>
> config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20261121/202611211941.G0rlpNpN-lkp@intel.com/config)
> compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 3b14d7c370558b46e5f0c6494a05c492e59bf32c)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261121/202611211941.G0rlpNpN-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/202611211941.G0rlpNpN-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
> >> drivers/s390/crypto/pkey_cca.c:22:45: error: array has incomplete element type 'struct ap_device_id'
>       22 | static struct ap_device_id pkey_cca_card_ids[] = {
>          |                                             ^
>    drivers/s390/crypto/ap_bus.h:158:9: note: forward declaration of 'struct ap_device_id'
>      158 |         struct ap_device_id *ids;
>          |                ^
>    1 error generated.
> --
> >> drivers/s390/crypto/pkey_ep11.c:23:46: error: array has incomplete element type 'struct ap_device_id'
>       23 | static struct ap_device_id pkey_ep11_card_ids[] = {
>          |                                              ^
>    drivers/s390/crypto/ap_bus.h:158:9: note: forward declaration of 'struct ap_device_id'
>      158 |         struct ap_device_id *ids;
>          |                ^
>    1 error generated.

That is fixed by [1] which is to be applied before the patch referenced
above.

[1]: https://lore.kernel.org/linux-kbuild/66e4ee9c7f9b4bc48fcee92a94b6bb6d92fe1ad2.1794233316.git.sashal@kernel.org/

-- 
Nicolas

      reply	other threads:[~2026-11-21 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261120202712.3377691-1-nsc@kernel.org>
2026-11-21 12:01 ` [PATCH] Move struct cpu_feature to a <linux/device-id/cpu_feature.h> kernel test robot
2026-11-21 12:51   ` Nicolas Schier [this message]

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=awGT4AhwcFcLsW0c@levanger \
    --to=nsc@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=bot@kernelci.org \
    --cc=chenhuacai@kernel.org \
    --cc=dengler@linux.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=kernel@xen0n.name \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=loongarch@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=u.kleine-koenig@baylibre.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