From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [kees:for-next/overflow 9/9] ./usr/include/misc/kunit.h:22:15: error: no macro name given in #define directive
Date: Mon, 28 Feb 2022 05:52:55 +0800 [thread overview]
Message-ID: <202202280550.gcosQL9r-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/overflow
head: 6a00c01f84e41b5cf50a312488cd72b5cd4e3d35
commit: 6a00c01f84e41b5cf50a312488cd72b5cd4e3d35 [9/9] UAPI: Introduce KUnit userspace compatibility
config: i386-randconfig-c001 (https://download.01.org/0day-ci/archive/20220228/202202280550.gcosQL9r-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=6a00c01f84e41b5cf50a312488cd72b5cd4e3d35
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees for-next/overflow
git checkout 6a00c01f84e41b5cf50a312488cd72b5cd4e3d35
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from <command-line>:32:
>> ./usr/include/misc/kunit.h:22:15: error: no macro name given in #define directive
22 | #define /**/
| ^
./usr/include/misc/kunit.h:144:12: warning: 'run_suites' defined but not used [-Wunused-function]
144 | static int run_suites(char *name, struct kunit_suite *suites[], size_t count)
| ^~~~~~~~~~
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-27 21:53 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=202202280550.gcosQL9r-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/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.