All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Pavan Chebbi <pavan.chebbi@broadcom.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	0day robot <lkp@intel.com>
Subject: ./usr/include/fwctl/bnxt.h:9:10: fatal error: 'linux/sizes.h' file not found
Date: Tue, 26 May 2026 17:02:52 +0200	[thread overview]
Message-ID: <202605261748.IIRSd9Bf-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Pavan-Chebbi/fwctl-Add-driver_data-field-to-fwctl_rpc/20260522-160839
head:   d6ce23e99fb2a6800a2af4ebb99cdcc9e6b06f4f
commit: d6ce23e99fb2a6800a2af4ebb99cdcc9e6b06f4f fwctl/bnxt: add DMA buffer support for HWRM commands
date:   4 days ago
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20260526/202605261748.IIRSd9Bf-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260526/202605261748.IIRSd9Bf-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/oe-kbuild-all/202605261748.IIRSd9Bf-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from <built-in>:1:
>> ./usr/include/fwctl/bnxt.h:9:10: fatal error: 'linux/sizes.h' file not found
       9 | #include <linux/sizes.h>
         |          ^~~~~~~~~~~~~~~
   1 error generated.

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

                 reply	other threads:[~2026-05-26 15:03 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=202605261748.IIRSd9Bf-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pavan.chebbi@broadcom.com \
    /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.