From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <linux@weissschuh.net>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/uapi-ucontext 2/2] arch/m68k/include/uapi/asm/ucontext.h:9:27: error: field 'uc_mcontext' has incomplete type
Date: Tue, 10 Mar 2026 06:26:57 +0800 [thread overview]
Message-ID: <202603100620.daXujbcR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/uapi-ucontext
head: 89dd25be8eeb8d7b52191bc5f82b7b5e7e5c216f
commit: b3b6bda8db008005cbd3da3b085bed301450704f [2/2] ucontext
config: m68k-allnoconfig (https://download.01.org/0day-ci/archive/20260310/202603100620.daXujbcR-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260310/202603100620.daXujbcR-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/202603100620.daXujbcR-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/m68k/include/asm/ucontext.h:8,
from arch/m68k/kernel/signal.c:51:
>> arch/m68k/include/uapi/asm/ucontext.h:9:27: error: field 'uc_mcontext' has incomplete type
9 | struct mcontext uc_mcontext;
| ^~~~~~~~~~~
vim +/uc_mcontext +9 arch/m68k/include/uapi/asm/ucontext.h
4
5 struct ucontext {
6 unsigned long uc_flags;
7 struct ucontext *uc_link;
8 stack_t uc_stack;
> 9 struct mcontext uc_mcontext;
10 unsigned long uc_filler[80];
11 sigset_t uc_sigmask; /* mask last for extensibility */
12 };
13
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-09 22:27 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=202603100620.daXujbcR-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux@weissschuh.net \
--cc=oe-kbuild-all@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 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.