From: Mark Rutland <mark.rutland@arm.com>, catalin.marinas@arm.com
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Chengming Zhou <zhouchengming@bytedance.com>,
mingo@redhat.com, will@kernel.org, tglx@linutronix.de,
dave.hansen@linux.intel.com, broonie@kernel.org, ardb@kernel.org,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, duanxiongchun@bytedance.com,
songmuchun@bytedance.com, zhengqi.arch@bytedance.com
Subject: Re: [PATCH v5 1/2] ftrace: cleanup ftrace_graph_caller enable and disable
Date: Fri, 29 Apr 2022 17:46:54 +0100 [thread overview]
Message-ID: <YmwWfsgiIDo9eoPw@FVFF77S0Q05N> (raw)
In-Reply-To: <20220425212707.378fb699@gandalf.local.home>
On Mon, Apr 25, 2022 at 09:27:07PM -0400, Steven Rostedt wrote:
> On Mon, 25 Apr 2022 10:51:19 +0100
> Mark Rutland <mark.rutland@arm.com> wrote:
>
> > Steve, are you happy if this goes via the arm64 tree along with patch 2?
>
> Yeah, go ahead.
>
> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Thanks!
Catalin, could you please pick these two?
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-29 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 16:00 [PATCH v5 1/2] ftrace: cleanup ftrace_graph_caller enable and disable Chengming Zhou
2022-04-20 16:00 ` [PATCH v5 2/2] arm64/ftrace: Make function graph use ftrace directly Chengming Zhou
2022-04-25 9:51 ` [PATCH v5 1/2] ftrace: cleanup ftrace_graph_caller enable and disable Mark Rutland
2022-04-26 1:27 ` Steven Rostedt
2022-04-29 16:46 ` Mark Rutland, catalin.marinas [this message]
2022-04-29 19:19 ` Catalin Marinas
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=YmwWfsgiIDo9eoPw@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=duanxiongchun@bytedance.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=songmuchun@bytedance.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@kernel.org \
--cc=zhengqi.arch@bytedance.com \
--cc=zhouchengming@bytedance.com \
/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