On 29.01.24 14:48, Baoquan He wrote:
On 01/29/24 at 08:12pm, kernel test robot wrote:
Hi Baoquan,
First bad commit (maybe != root cause):
tree: https://github.com/davidhildenbrand/linux fork_rmap_batching_mm_unstable
head: b652ec55c236cca5d0247cf66864971cc2ffea2d
commit: 21b8f7d4d9d70fec7ff6bbd973e485fa1226b156 [104/141] crash: remove dependency of FA_DUMP on CRASH_DUMP
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240129/202401292018.RTtZWk0P-lkp@xxxxxxxxx/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@xxxxxxxxx>
| Closes: https://lore.kernel.org/oe-kbuild-all/202401292018.RTtZWk0P-lkp@xxxxxxxxx/
All errors (new ones prefixed by >>):
......
make[4]: *** No rule to make target 'kernel/elfcorehdr.o', needed by 'kernel/built-in.a'.
This is fixed by Stephen at bottom. Now I can see it on linux-next:
Yes, thanks for the note (note that this branch was based on
mm-unstable, not linux-next directly), I spotted that yesterday as well
and got my builds going again. I think it's fixed in mm-unstable today
as well.
It's weird that the build bot sometimes only sends stuff related to my
WIP github branches to only me, but sometimes it decides to CC the MM
mailing list.
Anyhow, that ahead-of-submit buildbot runs on my branches is absolutely
fantastic, independent of who else gets CCed. (I still do cross-compiles
for weird architectures, but at least this way I get fast feedback for
the more common architectures)
--
Cheers,
David / dhildenb
