From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Willy Tarreau" <w@1wt.eu>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: don't use asm/ UAPI headers
Date: Fri, 7 Mar 2025 20:30:53 +0800 [thread overview]
Message-ID: <202503072041.LhDGl9Vn-lkp@intel.com> (raw)
In-Reply-To: <20250305-nolibc-asm-headers-v1-1-f2053def2ee7@linutronix.de>
Hi Thomas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on cb839e0cc881b4abd4a2e64cd06c2e313987a189]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Wei-schuh/tools-nolibc-don-t-use-asm-UAPI-headers/20250305-155035
base: cb839e0cc881b4abd4a2e64cd06c2e313987a189
patch link: https://lore.kernel.org/r/20250305-nolibc-asm-headers-v1-1-f2053def2ee7%40linutronix.de
patch subject: [PATCH] tools/nolibc: don't use asm/ UAPI headers
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
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/202503072041.LhDGl9Vn-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> tools/include/nolibc/sys.h: linux/signal.h is included more than once.
vim +14 tools/include/nolibc/sys.h
11
12 /* system includes */
13 #include <linux/unistd.h>
> 14 #include <linux/signal.h> /* for SIGCHLD */
15 #include <linux/termios.h>
16 #include <linux/mman.h>
17 #include <linux/fs.h>
18 #include <linux/loop.h>
19 #include <linux/time.h>
20 #include <linux/auxvec.h>
21 #include <linux/fcntl.h> /* for O_* and AT_* */
22 #include <linux/stat.h> /* for statx() */
23 #include <linux/prctl.h>
24 #include <linux/resource.h>
25 #include <linux/utsname.h>
> 26 #include <linux/signal.h>
27
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-03-07 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 7:48 Thomas Weißschuh
2025-03-07 12:30 ` kernel test robot [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=202503072041.LhDGl9Vn-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®