From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 9150/12133] /usr/s390x-linux-gnu/include/asm/sigcontext.h:73:9: error: unknown type name '__vector128'
Date: Sat, 04 Apr 2026 08:10:46 +0200 [thread overview]
Message-ID: <202604040819.Q90Gla3S-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Thomas Weißschuh" <linux@weissschuh.net>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 2febe6e6ee6e34c7754eff3c4d81aa7b0dcb7979
commit: 9b93f7e3277490f0356309c9b241eeeaa27ba859 [9150/12133] tools/getdelays: use the static UAPI headers from tools/include/uapi
:::::: branch date: 15 hours ago
:::::: commit date: 7 days ago
config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260404/202604040819.Q90Gla3S-lkp@intel.com/config)
compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260404/202604040819.Q90Gla3S-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/r/202604040819.Q90Gla3S-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from /usr/s390x-linux-gnu/include/bits/sigcontext.h:30,
from /usr/s390x-linux-gnu/include/signal.h:301,
from /usr/s390x-linux-gnu/include/sys/wait.h:36,
from getdelays.c:25:
>> /usr/s390x-linux-gnu/include/asm/sigcontext.h:73:9: error: unknown type name '__vector128'
73 | __vector128 vxrs_high[__NUM_VXRS_HIGH];
| ^~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-04 6:10 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=202604040819.Q90Gla3S-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox