Received-SPF: pass (google.com: domain of linux-kernel+bounces-201398-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <20240604212817.384103202@goodmis.org>
User-Agent: quilt/0.68
Date: Tue, 04 Jun 2024 17:28:17 -0400
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org,
 linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
 Mark Rutland <mark.rutland@arm.com>,
 Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
 Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/5] ftrace: Clean up and comment code
Precedence: bulk

While working on the function_graph multiple users code, I realized
that I was struggling with how the ftrace code worked. Being the
author of such code meant that it wasn't very intuitive. Namely, the
function names were not descriptive enough, or at least, they needed
comments.

This series moves to solve some of that via changing a couple function
names and parameters and adding comments to many of them.

There's more to do, but this at least moves it in the right direction.


Steven Rostedt (Google) (5):
      ftrace: Rename dup_hash() and comment it
      ftrace: Comment __ftrace_hash_rec_update() and make filter_hash bool
      ftrace: Remove "filter_hash" parameter from ftrace_hash_rec_disable/enable()
      ftrace: Convert "filter_hash" and "inc" to bool in ftrace_hash_rec_update_modify()
      ftrace: Add comments to ftrace_hash_move() and friends

----
 kernel/trace/ftrace.c | 103 +++++++++++++++++++++++++++++++++++++++++---------
 1 file changed, 86 insertions(+), 17 deletions(-)