From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Haiyue Wang <haiyuewa@163.com>,
x86@kernel.org, linux-trace-kernel@vger.kernel.org,
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>,
linux-kernel@vger.kernel.org (open list:FUNCTION HOOKS (FTRACE))
Subject: Re: [PATCH v1] ftrace: Fix compile error when CONFIG_GENDWARFKSYMS is enabled
Date: Thu, 6 Feb 2025 11:45:29 +0900 [thread overview]
Message-ID: <20250206114529.d2483df2c9d09726f1f3a43d@kernel.org> (raw)
In-Reply-To: <20250205195300.42d3e3b0@gandalf.local.home>
On Wed, 5 Feb 2025 19:53:00 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 6 Feb 2025 09:38:53 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
> > Thanks for the fix. And this fixes one of problems.
> > Another one is that `is_endbr()` is defined in <asm/ibt.h> but that also depend
> > on CONFIG_HAVE_FENTRY.
> >
> > Let's pick this and fix above issue.
>
> OK, I'll pull this into my urgent tree and start testing it.
Sorry, Gabriel found another issue.
Let me fix this instead of this patch.
https://lore.kernel.org/all/CAFEugPfFykYsHqS-J36CNWDn+d34bSQg-e5hJ=AaJPC8=6Ej-g@mail.gmail.com/
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-02-06 2:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 18:00 [PATCH v1] ftrace: Fix compile error when CONFIG_GENDWARFKSYMS is enabled Haiyue Wang
2025-02-05 18:51 ` Sami Tolvanen
2025-02-06 0:38 ` Masami Hiramatsu
2025-02-06 0:53 ` Steven Rostedt
2025-02-06 2:45 ` Masami Hiramatsu [this message]
2025-02-06 3:23 ` Haiyue Wang
2025-02-06 4:17 ` Masami Hiramatsu
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=20250206114529.d2483df2c9d09726f1f3a43d@kernel.org \
--to=mhiramat@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox