From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Nicolas Schier <nsc@kernel.org>
Subject: Re: [linux-next:master 3784/7428] include/linux/page-flags-layout.h:6:10: fatal error: 'generated/bounds.h' file not found
Date: Mon, 16 Nov 2026 12:28:24 +0100 [thread overview]
Message-ID: <avroMXSm8hiG1W4N@monoceros> (raw)
In-Reply-To: <202611160947.NOrZmI1p-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2316 bytes --]
On Mon, Nov 16, 2026 at 09:45:42AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 84abb955b1015477aa11a96e2f3ac1b938b77f48
> commit: cdfdbc11552b99dbc5c45c55f62a76527ffcc73d [3784/7428] Move struct cpu_feature to <linux/cpufeature.h>
> config: loongarch-defconfig (https://download.01.org/0day-ci/archive/20261116/202611160947.NOrZmI1p-lkp@intel.com/config)
> compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project ca14e3d05c4e63d6e8103945c86b958ed2f55d5f)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261116/202611160947.NOrZmI1p-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/202611160947.NOrZmI1p-lkp@intel.com/
>
> Note: the linux-next/master HEAD 84abb955b1015477aa11a96e2f3ac1b938b77f48 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> In file included from scripts/mod/devicetable-offsets.c:3:
> In file included from include/linux/cpufeature.h:30:
> In file included from arch/loongarch/include/asm/cpufeature.h:13:
> In file included from arch/loongarch/include/asm/elf.h:9:
> In file included from include/linux/fs.h:5:
> In file included from include/linux/fs/super.h:5:
> In file included from include/linux/fs/super_types.h:7:
> In file included from include/linux/list_lru.h:14:
> In file included from include/linux/xarray.h:16:
> In file included from include/linux/gfp.h:7:
> In file included from include/linux/mmzone.h:20:
> >> include/linux/page-flags-layout.h:6:10: fatal error: 'generated/bounds.h' file not found
> 6 | #include <generated/bounds.h>
> | ^~~~~~~~~~~~~~~~~~~~
> 1 error generated.
This is the issue that Sasha Levin already reported and fixed in the
thread about cdfdbc11552b99dbc5c45c55f62a76527ffcc73d, see
https://lore.kernel.org/all/f610c07f39df15f3e7ebdc63bfcd759ca7a687a8.1794233316.git.sashal@kernel.org/.
Nicolas claimed to have applied it already.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-11-16 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 1:45 [linux-next:master 3784/7428] include/linux/page-flags-layout.h:6:10: fatal error: 'generated/bounds.h' file not found kernel test robot
2026-11-16 11:28 ` Uwe Kleine-König (The Capable Hub) [this message]
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=avroMXSm8hiG1W4N@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nsc@kernel.org \
--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