From: Eric Biggers <ebiggers@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [linux-next:master 1651/2468] lib/crc/crc64-main.c:58:10: fatal error: 'crc64.h' file not found
Date: Sat, 14 Jun 2025 15:28:16 -0700 [thread overview]
Message-ID: <20250614222816.GA133549@quark> (raw)
In-Reply-To: <202506150606.rxZTzhKn-lkp@intel.com>
On Sun, Jun 15, 2025 at 06:13:34AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: bc6e0ba6c9bafa6241b05524b9829808056ac4ad
> commit: f58a15d5151d0d21b505ea43457f362cf0d75469 [1651/2468] lib/crc/x86: migrate x86-optimized CRC code into lib/crc/
> config: um-allmodconfig (https://download.01.org/0day-ci/archive/20250615/202506150606.rxZTzhKn-lkp@intel.com/config)
> compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250615/202506150606.rxZTzhKn-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/202506150606.rxZTzhKn-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> clang: warning: no such include directory: 'lib/crc/um' [-Wmissing-include-dirs]
> >> lib/crc/crc64-main.c:58:10: fatal error: 'crc64.h' file not found
> 58 | #include "crc64.h" /* $(SRCARCH)/crc64.h */
> | ^~~~~~~~~
> 1 error generated.
>
>
> vim +58 lib/crc/crc64-main.c
>
> e2fd1883971db5 Eric Biggers 2025-06-07 56
> e2fd1883971db5 Eric Biggers 2025-06-07 57 #ifdef CONFIG_CRC64_ARCH
> e2fd1883971db5 Eric Biggers 2025-06-07 @58 #include "crc64.h" /* $(SRCARCH)/crc64.h */
> e2fd1883971db5 Eric Biggers 2025-06-07 59 #else
> e2fd1883971db5 Eric Biggers 2025-06-07 60 #define crc64_be_arch crc64_be_generic
> e2fd1883971db5 Eric Biggers 2025-06-07 61 #define crc64_nvme_arch crc64_nvme_generic
> e2fd1883971db5 Eric Biggers 2025-06-07 62 #endif
> e2fd1883971db5 Eric Biggers 2025-06-07 63
>
> :::::: The code at line 58 was first introduced by commit
> :::::: e2fd1883971db5a2e3537f7deb6702056891d03f lib/crc: prepare for arch-optimized code in subdirs of lib/crc/
>
> :::::: TO: Eric Biggers <ebiggers@google.com>
> :::::: CC: Eric Biggers <ebiggers@google.com>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
Already fixed in crc-next by:
https://lore.kernel.org/r/20250612054514.142728-1-ebiggers@kernel.org/
- Eric
prev parent reply other threads:[~2025-06-14 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 22:13 [linux-next:master 1651/2468] lib/crc/crc64-main.c:58:10: fatal error: 'crc64.h' file not found kernel test robot
2025-06-14 22:28 ` Eric Biggers [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=20250614222816.GA133549@quark \
--to=ebiggers@kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=martin.petersen@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).