From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hverkuil-media-tree:extron 101/103] ./usr/include/linux/cec.h:150:19: error: unknown type name 'bool'
Date: Thu, 27 Jan 2022 00:59:43 +0800 [thread overview]
Message-ID: <202201270048.Xzuv297t-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
tree: git://linuxtv.org/hverkuil/media_tree.git extron
head: 54377f21d8b2084a9f5993230bdab8e8cd55bb22
commit: d679f6adf24b7fef91e8a3b3584b48587e9cf0a2 [101/103] cec.h: add cec_msg_recv_is_tx_result() helper
config: x86_64-randconfig-a004 (https://download.01.org/0day-ci/archive/20220127/202201270048.Xzuv297t-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
git remote add hverkuil-media-tree git://linuxtv.org/hverkuil/media_tree.git
git fetch --no-tags hverkuil-media-tree extron
git checkout d679f6adf24b7fef91e8a3b3584b48587e9cf0a2
# 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 errors (new ones prefixed by >>):
In file included from ./usr/include/linux/cec-funcs.h:11,
from <command-line>:32:
>> ./usr/include/linux/cec.h:150:19: error: unknown type name 'bool'
150 | static __inline__ bool cec_msg_recv_is_tx_result(const struct cec_msg *msg)
| ^~~~
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2022-01-26 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 16:59 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-26 22:16 [hverkuil-media-tree:extron 101/103] ./usr/include/linux/cec.h:150:19: error: unknown type name 'bool' kernel test robot
2022-01-26 22:16 ` 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=202201270048.Xzuv297t-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.