From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [mingo-tip:master 2300/2300] usr/include/linux/neighbour.h:9: found __[us]{8, 16, 32, 64} type without #include <linux/types.h>
Date: Sun, 09 Jan 2022 03:25:25 +0800 [thread overview]
Message-ID: <202201090323.0gexKYhO-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]
tree: git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git master
head: 4e348e961395297bb17f101cc63bc133d8a348e9
commit: 4e348e961395297bb17f101cc63bc133d8a348e9 [2300/2300] FIX: f989e243f1f4 headers/deps: uapi/headers: Create usr/include/uapi symbolic link
config: x86_64-randconfig-a014-20220108 (https://download.01.org/0day-ci/archive/20220109/202201090323.0gexKYhO-lkp(a)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/mingo/tip.git/commit/?id=4e348e961395297bb17f101cc63bc133d8a348e9
git remote add mingo-tip git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git
git fetch --no-tags mingo-tip master
git checkout 4e348e961395297bb17f101cc63bc133d8a348e9
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> usr/include/linux/neighbour.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h>
--
>> usr/include/linux/if_addr.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h>
--
>> usr/include/linux/netlink.h:40: found __[us]{8,16,32,64} type without #include <linux/types.h>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [mingo-tip:master 2300/2300] usr/include/linux/neighbour.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h>
Date: Sun, 9 Jan 2022 03:25:25 +0800 [thread overview]
Message-ID: <202201090323.0gexKYhO-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git master
head: 4e348e961395297bb17f101cc63bc133d8a348e9
commit: 4e348e961395297bb17f101cc63bc133d8a348e9 [2300/2300] FIX: f989e243f1f4 headers/deps: uapi/headers: Create usr/include/uapi symbolic link
config: x86_64-randconfig-a014-20220108 (https://download.01.org/0day-ci/archive/20220109/202201090323.0gexKYhO-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/mingo/tip.git/commit/?id=4e348e961395297bb17f101cc63bc133d8a348e9
git remote add mingo-tip git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git
git fetch --no-tags mingo-tip master
git checkout 4e348e961395297bb17f101cc63bc133d8a348e9
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> usr/include/linux/neighbour.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h>
--
>> usr/include/linux/if_addr.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h>
--
>> usr/include/linux/netlink.h:40: found __[us]{8,16,32,64} type without #include <linux/types.h>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-01-08 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 19:25 kernel test robot [this message]
2022-01-08 19:25 ` [mingo-tip:master 2300/2300] usr/include/linux/neighbour.h:9: found __[us]{8,16,32,64} type without #include <linux/types.h> 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=202201090323.0gexKYhO-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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.