0 day kernel build service
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [mda-next:icssg-dev 13/15] hsr_ptp_test.c:297:35: error: unknown type name 'bool'
Date: Tue, 28 Jul 2026 12:06:52 +0200	[thread overview]
Message-ID: <202607281205.aZmuCDpi-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
CC: MD Danish Anwar <danishanwar@ti.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mda/linux-next.git icssg-dev
head:   9f0cef2c942f471aa9823635ff26c85e6e667056
commit: 30e1205e7c0df4aa1557ab2718cc402a0c086618 [13/15] selftests: hsr: Add test for the inline PTP header on HSR
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260728/202607281205.aZmuCDpi-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260728/202607281205.aZmuCDpi-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/202607281205.aZmuCDpi-lkp@intel.com/

Note: the mda-next/icssg-dev HEAD 9f0cef2c942f471aa9823635ff26c85e6e667056 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

>> hsr_ptp_test.c:297:35: error: unknown type name 'bool'
     297 | static int32_t pkt_send(int port, bool hsr_hdr, void *data, int data_len)
         |                                   ^~~~
   hsr_ptp_test.c:22:1: note: 'bool' is defined in header '<stdbool.h>'; this is probably fixable by adding '#include <stdbool.h>'
      21 | #include <sys/ioctl.h>
     +++ |+#include <stdbool.h>
      22 | 
   hsr_ptp_test.c: In function 'main':
>> hsr_ptp_test.c:395:13: error: implicit declaration of function 'pkt_send' [-Wimplicit-function-declaration]
     395 |         if (pkt_send(PORT_1, false, ptp_packet, sizeof(ptp_packet)) < 0) {
         |             ^~~~~~~~
>> hsr_ptp_test.c:395:30: error: 'false' undeclared (first use in this function)
     395 |         if (pkt_send(PORT_1, false, ptp_packet, sizeof(ptp_packet)) < 0) {
         |                              ^~~~~
   hsr_ptp_test.c:395:30: note: 'false' is defined in header '<stdbool.h>'; this is probably fixable by adding '#include <stdbool.h>'
   hsr_ptp_test.c:395:30: note: each undeclared identifier is reported only once for each function it appears in
>> hsr_ptp_test.c:417:30: error: 'true' undeclared (first use in this function)
     417 |         if (pkt_send(PORT_1, true, ptp_packet, sizeof(ptp_packet)) < 0) {
         |                              ^~~~
   hsr_ptp_test.c:417:30: note: 'true' is defined in header '<stdbool.h>'; this is probably fixable by adding '#include <stdbool.h>'

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-28 10:07 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=202607281205.aZmuCDpi-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox