From: kernel test robot <lkp@intel.com>
To: Kyle Sanderson <kyle.leet@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:pr/1103 1/1] fs/bcachefs/alloc/zone.c:23:10: fatal error: 'linux/printbuf.h' file not found
Date: Tue, 07 Apr 2026 12:04:02 +0800 [thread overview]
Message-ID: <202604071152.iDI82zbN-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs pr/1103
head: 773a9613b5d5dea295b8faadab583519fdbbaccf
commit: 5c65ed577ff88f1ef3236caa947c006c4131dc5f [1/1] wip: defrag
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20260407/202604071152.iDI82zbN-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260407/202604071152.iDI82zbN-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/202604071152.iDI82zbN-lkp@intel.com/
Note: the koverstreet-bcachefs/pr/1103 HEAD 773a9613b5d5dea295b8faadab583519fdbbaccf builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> fs/bcachefs/alloc/zone.c:23:10: fatal error: 'linux/printbuf.h' file not found
23 | #include <linux/printbuf.h>
| ^~~~~~~~~~~~~~~~~~
1 error generated.
vim +23 fs/bcachefs/alloc/zone.c
20
21 #include <linux/math64.h>
22 #include <linux/log2.h>
> 23 #include <linux/printbuf.h>
24
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 4:04 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=202604071152.iDI82zbN-lkp@intel.com \
--to=lkp@intel.com \
--cc=kyle.leet@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@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