[GIT,PULL] Please pull powerpc/linux.git powerpc-5.17-5 tag

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Linus,

Please pull another powerpc fix for 5.17:

The following changes since commit fe663df7825811358531dc2e8a52d9eaa5e3515e:

  powerpc/lib/sstep: fix 'ptesync' build error (2022-02-15 22:31:35 +1100)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.17-5

for you to fetch changes up to 58dbe9b373df2828d873b1c0e5afc77485b2f376:

  powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set (2022-03-05 20:42:21 +1100)

- ------------------------------------------------------------------
powerpc fixes for 5.17 #5

Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set.

Thanks to: Murilo Opsfelder Araujo, Erhard F.

- ------------------------------------------------------------------
Murilo Opsfelder Araujo (1):
      powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set


 arch/powerpc/include/asm/book3s/64/mmu.h | 2 +-
 arch/powerpc/include/asm/kexec_ranges.h  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmIkZ+cACgkQUevqPMjh
pYCF1BAAnmZb6JbgLgztefPUyq9mx0q5FqcCqAhj6I+x/8T4qBGawbFpqazW6BIm
i1vHp2Yrj+S86qDQLo33LzO4nKK+EMDhgCAjFpryD8Kla0wDHBYDZy6JMd7LDYao
+j0EBB3w+HOWIUB50fb6EbEgRUFA1gMK4UaOxDRW5dnZCJ7h2qWB5Yev4i1Lzkmb
tPMvfPQYqMjzEcdMt07m7qHG72VxyBUgQbSMhE7VSKjmp9/oNPzxFFBmA0HoX6md
0pwXfXtvnVnMboSTHBYe6Ohk+kdA2P8P7agn/TW0kENP+RM+KePWVOAvAfqPjYCJ
dmqQsmn5ar46tlpPTS834ErDlCNNmfWuNAVILxUt3hQOyHQn4lDDZLR6EDKX22GX
OV9Hth5VPKqkiz8PmGAgcTE+A0s+kGU8DZN9LZefyBLV3Wb5/gHuxQFn8SCX71aE
EtcPJTP7IxZN8epI0b0ZEwM88i6RtFcteAlwYErGe9/UYBJK91zHj4FMWf83BI73
tmJkaVcDDezsbKGuibj3THB5SgzCcp/W5FrPjHWGXbrtYvjGuYp0HKraMGiLimlo
QV3uB/j7qMK0zHBXcypH0P6RrNN3NlaFiSMdl7KrdeWEsaGN8dQ8vKDYo3gJSKF+
lbUkYQV0d6RvHVZvgT11WC9o1SoKH2V5n9OGKNKUmz4RquAbCd8=
=7GLj
-----END PGP SIGNATURE-----

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