[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20230622101420.f50c8d702a5757647b92250a@linux-foundation.org>
Date: Thu, 22 Jun 2023 10:14:20 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Petr Mladek <pmladek@...e.com>
Cc: Douglas Anderson <dianders@...omium.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 Thu, 22 Jun 2023 10:40:11 +0200 Petr Mladek <pmladek@...e.com> wrote:
> 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.
7ca8fe94aa92 is now in the mm-stable branch, which is is non-rebasing,
so this hash should be good.
Patches get moved from the rebasing mm-unstable to the non-rebasing
mm-stable when they're considered to be stabilized.
Ditto mm-hotfixes-unstable/mm-hotfixes-stable and
mm-nonmm-unstable/mm-nonmm-stable.
Powered by blists - more mailing lists