[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJQI6_P2yfJKZK52@alley>
Date: Thu, 22 Jun 2023 10:40:11 +0200
From: Petr Mladek <pmladek@...e.com>
To: Douglas Anderson <dianders@...omium.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Michael Ellerman <mpe@...erman.id.au>,
Arnd Bergmann <arnd@...db.de>,
Christophe Leroy <christophe.leroy@...roup.eu>,
Laurent Dufour <ldufour@...ux.ibm.com>,
Nicholas Piggin <npiggin@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Tom Rix <trix@...hat.com>, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH] powerpc: Move arch_trigger_cpumask_backtrace from nmi.h
to irq.h
On Wed 2023-06-21 16:48:19, Douglas Anderson wrote:
> The powerpc architecture was the only one that defined
> arch_trigger_cpumask_backtrace() in asm/nmi.h instead of
> asm/irq.h. Move it to be consistent.
>
> This fixes compile time errors introduced by commit 7ca8fe94aa92
> ("watchdog/hardlockup: define HARDLOCKUP_DETECTOR_ARCH"). That commit
Will this commit end up in the mainline wihtout rebasing?
We could use only final commit hashes in the commit messages.
> caused <asm/nmi.h> to stop being included if the hardlockup detector
> wasn't enabled. The specific errors were:
> error: implicit declaration of function ‘nmi_cpu_backtrace’
> error: implicit declaration of function ‘nmi_trigger_cpumask_backtrace’
>
> Fixes: 7ca8fe94aa92 ("watchdog/hardlockup: define HARDLOCKUP_DETECTOR_ARCH")
> Reported-by: Michael Ellerman <mpe@...erman.id.au>
> Closes: https://lore.kernel.org/r/871qi5otdh.fsf@mail.lhotse
> Signed-off-by: Douglas Anderson <dianders@...omium.org>
Looks like a reasonable solution:
Reviewed-by: Petr Mladek <pmladek@...e.com>
Thanks a lot for fixing the regression.
Best Regards,
Petr
Powered by blists - more mailing lists