[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250711112844.GG1099709@noisy.programming.kicks-ass.net>
Date: Fri, 11 Jul 2025 13:28:44 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Nam Cao <namcao@...utronix.de>
Cc: Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Gabriele Monaco <gmonaco@...hat.com>,
linux-trace-kernel@...r.kernel.org,
Josh Poimboeuf <jpoimboe@...nel.org>,
Petr Mladek <pmladek@...e.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Fix up build issues with vpanic
On Fri, Jul 11, 2025 at 01:20:41PM +0200, Nam Cao wrote:
> Hi,
>
> The newly introduced vpanic() has some build issues. This series fix them
> up.
>
> As the vpanic() is only in ftrace tree for now, it is probably best to let
> this series goes to ftrace tree, if everyone is okay with that.
Does it make sense to make panic a static inline?
Powered by blists - more mailing lists