Message ID | 87bkyjo6wn.fsf@mpe.ellerman.id.au (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
Series | [GIT,PULL] Please pull powerpc/linux.git powerpc-5.17-5 tag | expand |
On Sat, Mar 5, 2022 at 11:51 PM Michael Ellerman <mpe@ellerman.id.au> wrote: > > powerpc fixes for 5.17 #5 > > Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set. Hmm. I'm *still* not seeing the fix for the reported powerpc:skiroot_defconfig failure: arch/powerpc/kernel/stacktrace.c: In function 'handle_backtrace_ipi': arch/powerpc/kernel/stacktrace.c:171:9: error: implicit declaration of function 'nmi_cpu_backtrace' which has been pending forever. The alleged fix (commit 5a72345e6a78: "powerpc: Fix STACKTRACE=n build") has been in linux-next for three weeks by now, but hasn't been sent to me. And you must be aware of it, since you're the author, signed off on it and committed it. What's up? This has been reported forever, and was already failing in rc2. I'm about to release rc7 and it's *still* there. Linus
The pull request you sent on Sun, 06 Mar 2022 18:51:36 +1100:
> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.17-5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9bdeaca18bf61d55029277bb35f72c2002c88c4d
Thank you!
Linus Torvalds <torvalds@linux-foundation.org> writes: > On Sat, Mar 5, 2022 at 11:51 PM Michael Ellerman <mpe@ellerman.id.au> wrote: >> >> powerpc fixes for 5.17 #5 >> >> Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set. > > Hmm. > > I'm *still* not seeing the fix for the reported > powerpc:skiroot_defconfig failure: > > arch/powerpc/kernel/stacktrace.c: In function 'handle_backtrace_ipi': > arch/powerpc/kernel/stacktrace.c:171:9: error: implicit > declaration of function 'nmi_cpu_backtrace' > > which has been pending forever. > > The alleged fix (commit 5a72345e6a78: "powerpc: Fix STACKTRACE=n > build") has been in linux-next for three weeks by now, but hasn't been > sent to me. And you must be aware of it, since you're the author, > signed off on it and committed it. > > What's up? This has been reported forever, and was already failing in > rc2. I'm about to release rc7 and it's *still* there. Yeah, hmm indeed. It's in my next branch, not my fixes branch. That's why you see it in linux-next. I don't recall why I put it in next, possibly I thought it wasn't a regression in this release, but I may have just put it in next by accident. I'll cherry pick it into fixes and send it to you before the release. cheers