From: Mark Rutland <mark.rutland@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Florent Revest <revest@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mhiramat@kernel.org, ast@kernel.org, daniel@iogearbox.net,
kpsingh@kernel.org, jolsa@kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 0/7] Refactor ftrace direct call APIs
Date: Fri, 24 Mar 2023 11:46:31 +0000 [thread overview]
Message-ID: <ZB2Nl7fzpHoq5V20@FVFF77S0Q05N> (raw)
In-Reply-To: <20230323220042.40ec4904@gandalf.local.home>
On Thu, Mar 23, 2023 at 10:00:42PM -0400, Steven Rostedt wrote:
> On Thu, 23 Mar 2023 19:43:55 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Since that commit only contains the updates for the direct trampolines that
> > ARM64 needs, and I'm not going to rebase that branch, you can just merge it
> > into the ARM64 tree so that you can base your changes on it. Make sure you
> > merge that commit, not the branch, as I have more tracing specific patches
> > on top of that commit.
>
> I just made it easier for you. I created a signed tag: trace-direct-v6.3-rc3
>
> So just pull from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
>
> tag: trace-direct-v6.3-rc3
Thanks Steve; much appreciated!
Florent, can you post a new spinf of the remaining arm64 bits rebased atop
that?
Thanks,
Mark.
next prev parent reply other threads:[~2023-03-24 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 14:04 [PATCH v2 0/7] Refactor ftrace direct call APIs Florent Revest
2023-03-21 14:04 ` [PATCH v2 1/7] ftrace: Let unregister_ftrace_direct_multi() call ftrace_free_filter() Florent Revest
2023-03-21 14:04 ` [PATCH v2 2/7] ftrace: Replace uses of _ftrace_direct APIs with _ftrace_direct_multi Florent Revest
2023-03-21 14:04 ` [PATCH v2 3/7] ftrace: Remove the legacy _ftrace_direct API Florent Revest
2023-03-21 14:04 ` [PATCH v2 4/7] ftrace: Rename _ftrace_direct_multi APIs to _ftrace_direct APIs Florent Revest
2023-03-21 14:04 ` [PATCH v2 5/7] ftrace: Store direct called addresses in their ops Florent Revest
2023-03-21 14:04 ` [PATCH v2 6/7] ftrace: Make DIRECT_CALLS work WITH_ARGS and !WITH_REGS Florent Revest
2023-03-21 14:04 ` [PATCH v2 7/7] ftrace: selftest: remove broken trace_direct_tramp Florent Revest
2023-03-21 17:06 ` [PATCH v2 0/7] Refactor ftrace direct call APIs Jiri Olsa
2023-03-23 23:43 ` Steven Rostedt
2023-03-24 2:00 ` Steven Rostedt
2023-03-24 11:46 ` Mark Rutland [this message]
2023-03-24 17:18 ` Florent Revest
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=ZB2Nl7fzpHoq5V20@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=revest@chromium.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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