From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-renesas-soc@vger.kernel.org
Subject: [geert-renesas-devel:master] BUILD REGRESSION 8e27b1d4225c6a239971725fb12a477f99fc4b64
Date: Tue, 24 Jan 2023 09:32:59 +0800 [thread overview]
Message-ID: <63cf354b./7UCCbDxzGWplUEx%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git master
branch HEAD: 8e27b1d4225c6a239971725fb12a477f99fc4b64 Merge branch 'renesas-next' into renesas-devel
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202301240428.nR3yBWOD-lkp@intel.com
https://lore.kernel.org/oe-kbuild-all/202301240450.yiHTqTmb-lkp@intel.com
Error/Warning: (recently discovered and may have been fixed)
drivers/block/pktcdvd.c:49:10: fatal error: 'linux/pktcdvd.h' file not found
drivers/block/pktcdvd.c:49:10: fatal error: linux/pktcdvd.h: No such file or directory
Error/Warning ids grouped by kconfigs:
gcc_recent_errors
|-- alpha-randconfig-r026-20230123
| `-- drivers-block-pktcdvd.c:fatal-error:linux-pktcdvd.h:No-such-file-or-directory
|-- i386-randconfig-m021-20230123
| `-- drivers-block-pktcdvd.c:fatal-error:linux-pktcdvd.h:No-such-file-or-directory
|-- m68k-allmodconfig
| `-- drivers-block-pktcdvd.c:fatal-error:linux-pktcdvd.h:No-such-file-or-directory
`-- sh-allmodconfig
`-- drivers-block-pktcdvd.c:fatal-error:linux-pktcdvd.h:No-such-file-or-directory
clang_recent_errors
`-- x86_64-rhel-8.3-rust
`-- drivers-block-pktcdvd.c:fatal-error:linux-pktcdvd.h-file-not-found
elapsed time: 726m
configs tested: 62
configs skipped: 2
gcc tested configs:
powerpc allnoconfig
x86_64 allnoconfig
um x86_64_defconfig
um i386_defconfig
m68k allmodconfig
x86_64 defconfig
alpha allyesconfig
sh allmodconfig
arc allyesconfig
arc defconfig
i386 defconfig
s390 allmodconfig
powerpc allmodconfig
mips allyesconfig
alpha defconfig
i386 randconfig-a004-20230123
x86_64 rhel-8.3-syz
i386 randconfig-a003-20230123
s390 defconfig
x86_64 randconfig-a002-20230123
ia64 allmodconfig
i386 allyesconfig
x86_64 rhel-8.3-kunit
arc randconfig-r043-20230123
x86_64 rhel-8.3
i386 randconfig-a002-20230123
x86_64 randconfig-a001-20230123
s390 allyesconfig
x86_64 rhel-8.3-kvm
arm randconfig-r046-20230123
x86_64 rhel-8.3-kselftests
m68k allyesconfig
arm defconfig
i386 randconfig-a001-20230123
x86_64 rhel-8.3-bpf
x86_64 rhel-8.3-func
x86_64 randconfig-a006-20230123
i386 randconfig-a005-20230123
x86_64 randconfig-a004-20230123
i386 randconfig-a006-20230123
x86_64 randconfig-a003-20230123
x86_64 randconfig-a005-20230123
x86_64 allyesconfig
arm allyesconfig
arm64 allyesconfig
clang tested configs:
hexagon randconfig-r041-20230123
hexagon randconfig-r045-20230123
i386 randconfig-a012-20230123
i386 randconfig-a013-20230123
riscv randconfig-r042-20230123
s390 randconfig-r044-20230123
i386 randconfig-a011-20230123
i386 randconfig-a014-20230123
x86_64 rhel-8.3-rust
i386 randconfig-a016-20230123
i386 randconfig-a015-20230123
x86_64 randconfig-a013-20230123
x86_64 randconfig-a011-20230123
x86_64 randconfig-a012-20230123
x86_64 randconfig-a014-20230123
x86_64 randconfig-a016-20230123
x86_64 randconfig-a015-20230123
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2023-01-24 1:33 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=63cf354b./7UCCbDxzGWplUEx%lkp@intel.com \
--to=lkp@intel.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox