From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Nam Cao <namcao@linutronix.de>,
John Ogness <john.ogness@linutronix.de>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Gabriele Monaco <gmonaco@redhat.com>,
linux-trace-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@kernel.org>,
Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix up build issues with vpanic
Date: Fri, 11 Jul 2025 20:18:45 +0200 [thread overview]
Message-ID: <20250711181845.GA4105545@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250711122413.15b8456f@batman.local.home>
On Fri, Jul 11, 2025 at 12:24:13PM -0400, Steven Rostedt wrote:
> On Fri, 11 Jul 2025 13:20:41 +0200
> Nam Cao <namcao@linutronix.de> 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.
>
> Since the bug is in my tree I'll take it, but can I get an acked-by
> from Peter or Josh?
Sure
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
prev parent reply other threads:[~2025-07-11 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 11:20 Nam Cao
2025-07-11 11:20 ` [PATCH 1/2] objtool: Add vpanic() to the noreturn list Nam Cao
2025-07-11 11:20 ` [PATCH 2/2] panic: Fix up description of vpanic() Nam Cao
2025-07-15 5:56 ` Masami Hiramatsu
2025-07-15 13:31 ` Nam Cao
2025-07-11 11:28 ` [PATCH 0/2] Fix up build issues with vpanic Peter Zijlstra
2025-07-11 12:06 ` Nam Cao
2025-07-11 16:24 ` Steven Rostedt
2025-07-11 18:18 ` Peter Zijlstra [this message]
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=20250711181845.GA4105545@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gmonaco@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namcao@linutronix.de \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®