From: Peter Zijlstra <peterz@infradead.org>
To: Haiyue Wang <haiyuewa@163.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Gabriel de Perthuis <g2p.code@gmail.com>,
Sami Tolvanen <samitolvanen@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-trace-kernel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ftrace: x86: Fix a compile error about get_kernel_nofault()
Date: Fri, 7 Feb 2025 11:09:27 +0100 [thread overview]
Message-ID: <20250207100927.GB7145@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <b4ef10d0-a1eb-4d9c-8ddc-d7815a2bb607@163.com>
On Thu, Feb 06, 2025 at 09:25:37PM +0800, Haiyue Wang wrote:
> > --- a/arch/x86/include/asm/ftrace.h
> > +++ b/arch/x86/include/asm/ftrace.h
> > @@ -2,6 +2,7 @@
> > #ifndef _ASM_X86_FTRACE_H
> > #define _ASM_X86_FTRACE_H
> > +#include "asm/ibt.h"
Argh yes, I don't know where that came from. /me zaps
next prev parent reply other threads:[~2025-02-07 10:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 3:12 [PATCH] ftrace: x86: Fix a compile error about get_kernel_nofault() Masami Hiramatsu (Google)
2025-02-06 8:12 ` Peter Zijlstra
2025-02-06 11:54 ` Masami Hiramatsu
2025-02-06 12:13 ` Peter Zijlstra
2025-02-06 12:33 ` Peter Zijlstra
2025-02-06 13:25 ` Haiyue Wang
2025-02-07 10:09 ` Peter Zijlstra [this message]
2025-02-06 23:59 ` Masami Hiramatsu
2025-02-10 22:30 ` Steven Rostedt
2025-02-11 10:09 ` Peter Zijlstra
2025-02-11 15:50 ` Steven Rostedt
2025-02-12 16:52 ` Sami Tolvanen
2025-02-13 10:08 ` Peter Zijlstra
2025-02-13 10:25 ` Haiyue Wang
2025-02-13 10:40 ` Peter Zijlstra
2025-02-13 10:50 ` Haiyue Wang
2025-02-13 10:26 ` Peter Zijlstra
2025-02-13 13:35 ` Masami Hiramatsu
2025-02-13 0:03 ` Masami Hiramatsu
2025-02-06 18:19 ` Gabriel de Perthuis
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=20250207100927.GB7145@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=g2p.code@gmail.com \
--cc=haiyuewa@163.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.