> > There's another possibly relevant report for riscv: > > https://lore.kernel.org/r/202403090900.OwPqmRuI-lkp@xxxxxxxxx > > I think I messed up the nopmd use case. Since this commit already landed > mm-stable, I assume there's no way I provide a fixup. > > I attached a formal patch below, but I don't know how to test it myself, What I do: Grab https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/13.2.0/x86_64-gcc-13.2.0-nolibc-aarch64-linux.tar.gz untar that into /opt/crosstool And my crufty old script does, partly, WHAT="$*" ... [ $ARCH = arm64 ] && CT=gcc-13.2.0-nolibc && XARCH=aarch64-linux ... PATH=$PATH:/opt/crosstool/$CT/$XARCH/bin export PATH export CROSS_COMPILE=/opt/crosstool/$CT/$XARCH/bin/$XARCH- export CC="/opt/crosstool/$CT/$XARCH/bin/$XARCH-gcc" J=$(grep "^processor" /proc/cpuinfo | wc -l) J=$(expr $J \* 2) nice -20 make -j$J CC="$CC" $WHAT 2>/tmp/log-$ARCH setenv ARCH arm64 crufty-old-script vmlinux modules > and I'm not 100% confident. Before I post a formal patch, can anyone let > me know how I can kickoff the test bot to test the patch (or help me do the > kickoff)? Worked for me, thanks.
