[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250211100914.GA29593@noisy.programming.kicks-ass.net>
Date: Tue, 11 Feb 2025 11:09:14 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>,
Gabriel de Perthuis <g2p.code@...il.com>,
Haiyue Wang <haiyuewa@....com>,
Sami Tolvanen <samitolvanen@...gle.com>,
Mark Rutland <mark.rutland@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-trace-kernel@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ftrace: x86: Fix a compile error about
get_kernel_nofault()
On Mon, Feb 10, 2025 at 05:30:16PM -0500, Steven Rostedt wrote:
> On Fri, 7 Feb 2025 08:59:59 +0900
> Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
>
> > Ah, this looks good to me except for the removing redundant asm/ibt.h
> > which Haiyue pointed.
> >
> > Acked-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
>
> Cool, so Peter's going to fix this and I can drop the fixes that are in
> patchwork?
I was aiming my patch for x86/core, but if there's a reason to expedite
them, I can stick it in x86/urgent I suppose.
Just need a reason -- what's this compile error nonsense about, my
kernels build just fine?
Powered by blists - more mailing lists