public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	muriloo@linux.ibm.com
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-5 tag
Date: Mon, 07 Mar 2022 10:27:31 +1100	[thread overview]
Message-ID: <878rtmoe58.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CAHk-=whEQRDQ3fJT1KVVAeaWiJ+mYTM+MwYoXEOUQrnbERLa5w@mail.gmail.com>

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

  reply	other threads:[~2022-03-06 23:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06  7:51 [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-5 tag Michael Ellerman
2022-03-06 20:00 ` Linus Torvalds
2022-03-06 23:27   ` Michael Ellerman [this message]
2022-03-06 20:34 ` pr-tracker-bot

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=878rtmoe58.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=muriloo@linux.ibm.com \
    --cc=torvalds@linux-foundation.org \
    /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