public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Will Deacon <will@kernel.org>,
	Puranjay Mohan <puranjay@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	"Madhavan T. Venkataraman" <madvenka@linux.microsoft.com>,
	Kalesh Singh <kaleshsingh@google.com>,
	chenqiwu <qiwuchen55@gmail.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, puranjay12@gmail.com
Subject: Re: [PATCH] arm64: stacktrace: fix the usage of ftrace_graph_ret_addr()
Date: Wed, 4 Sep 2024 12:51:46 -0400	[thread overview]
Message-ID: <20240904125146.79859e7f@gandalf.local.home> (raw)
In-Reply-To: <20240904125000.4261b234@gandalf.local.home>

On Wed, 4 Sep 2024 12:50:00 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> > Ah, I didn't check to see if it was sent to linux-trace-kernel, so it
> > wasn't in patchwork, hence I forgot :-p
> > 
> > I can add it this week.
> >   
> 
> Actually, the code is in Linus's tree now, so it's probably better if it
> goes through your tree.
> 
> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> 

And you may want to add:

Fixes: 29c1c24a2707 ("function_graph: Fix up ftrace_graph_ret_addr()")

so that it gets backported with if that change gets backported.

-- Steve


  reply	other threads:[~2024-09-04 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 16:23 [PATCH] arm64: stacktrace: fix the usage of ftrace_graph_ret_addr() Puranjay Mohan
2024-06-18 16:50 ` Steven Rostedt
2024-06-18 17:42 ` Mark Rutland
2024-06-19 12:43   ` Will Deacon
2024-06-24 20:17     ` Steven Rostedt
2024-08-29 17:54       ` Mark Rutland
2024-09-03 20:07         ` Steven Rostedt
2024-09-04 16:50           ` Steven Rostedt
2024-09-04 16:51             ` Steven Rostedt [this message]
2024-09-05 17: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=20240904125146.79859e7f@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=catalin.marinas@arm.com \
    --cc=kaleshsingh@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madvenka@linux.microsoft.com \
    --cc=mark.rutland@arm.com \
    --cc=puranjay12@gmail.com \
    --cc=puranjay@kernel.org \
    --cc=qiwuchen55@gmail.com \
    --cc=will@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