0 day kernel build service
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [thomas-weissschuh:b4/uapi-ucontext 9/9] usr/include/asm/uctx.h:67:9: error: unknown type name 'sigset_t'
Date: Mon, 22 Jun 2026 23:03:08 +0800	[thread overview]
Message-ID: <202606222253.WOUHTXhA-lkp@intel.com> (raw)

:::::: 
:::::: 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>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/uapi-ucontext
head:   91307027b05329242e33a446a5a74aca50ec6322
commit: 91307027b05329242e33a446a5a74aca50ec6322 [9/9] kbuild: uapi: test-compile asm/ucontext.h
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: sparc-randconfig-001-20260622 (https://download.01.org/0day-ci/archive/20260622/202606222253.WOUHTXhA-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260622/202606222253.WOUHTXhA-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/202606222253.WOUHTXhA-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from ./usr/include/asm/ucontext.h:3,
                    from <command-line>:
>> usr/include/asm/uctx.h:67:9: error: unknown type name 'sigset_t'
      67 |         sigset_t                uc_sigmask;
         |         ^~~~~~~~

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

                 reply	other threads:[~2026-06-22 15:03 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=202606222253.WOUHTXhA-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