From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [thomas-weissschuh:b4/kbuild-uapi-libc 5/7] usr/dummy-include/string.h:1: error: header guard '_DUMMY_STRING_H' followed by '#define' of a different macro
Date: Sun, 25 Jan 2026 13:22:54 +0800 [thread overview]
Message-ID: <202601251331.LbuvwpRe-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/kbuild-uapi-libc
head: 42f8899f5959bce93a899d194c5b14d2a809bd31
commit: dad08d57845cdf10080325af1084b1a1f6bfc05f [5/7] can compile
:::::: branch date: 14 hours ago
:::::: commit date: 14 hours ago
config: m68k-allmodconfig (https://download.01.org/0day-ci/archive/20260125/202601251331.LbuvwpRe-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/20260125/202601251331.LbuvwpRe-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/202601251331.LbuvwpRe-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from ./usr/include/linux/string.h:7,
from <command-line>:
>> usr/dummy-include/string.h:1: error: header guard '_DUMMY_STRING_H' followed by '#define' of a different macro [-Werror=header-guard]
1 | #ifndef _DUMMY_STRING_H
usr/dummy-include/string.h:2: note: '_DUMMY_STRIGN_H' is defined here; did you mean '_DUMMY_STRING_H'?
2 | #define _DUMMY_STRIGN_H
cc1: all warnings being treated as errors
vim +1 usr/dummy-include/string.h
c2504abf729a15 Thomas Weißschuh 2026-01-24 @1 #ifndef _DUMMY_STRING_H
c2504abf729a15 Thomas Weißschuh 2026-01-24 2 #define _DUMMY_STRIGN_H
c2504abf729a15 Thomas Weißschuh 2026-01-24 3
:::::: The code at line 1 was first introduced by commit
:::::: c2504abf729a15f7df4bff328def344426a2b6da dummy includes
:::::: TO: Thomas Weißschuh <linux@weissschuh.net>
:::::: CC: Thomas Weißschuh <linux@weissschuh.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-25 5:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 5:22 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-25 6:32 [thomas-weissschuh:b4/kbuild-uapi-libc 5/7] usr/dummy-include/string.h:1: error: header guard '_DUMMY_STRING_H' followed by '#define' of a different macro kernel test robot
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=202601251331.LbuvwpRe-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 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.