The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, mhiramat@kernel.org, revest@chromium.org,
	rostedt@goodmis.org, linux-trace-kernel@vger.kernel.org
Subject: [PATCH v2 1/3] ftrace: Maintain samples/ftrace
Date: Tue,  3 Jan 2023 12:49:10 +0000	[thread overview]
Message-ID: <20230103124912.2948963-2-mark.rutland@arm.com> (raw)
In-Reply-To: <20230103124912.2948963-1-mark.rutland@arm.com>

There's no entry in MAINTAINERS for samples/ftrace. Add one so that the
FTRACE maintainers are kept in the loop.

Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 7f86d02cb427a..739006e245fbd 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8571,6 +8571,7 @@ F:	kernel/trace/fgraph.c
 F:	arch/*/*/*/*ftrace*
 F:	arch/*/*/*ftrace*
 F:	include/*/ftrace.h
+F:	samples/ftrace
 
 FUNGIBLE ETHERNET DRIVERS
 M:	Dimitris Michailidis <dmichail@fungible.com>
-- 
2.30.2


  reply	other threads:[~2023-01-03 12:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 12:49 [PATCH v2 0/3] ftrace: Add sample code with dynamic ftrace_ops Mark Rutland
2023-01-03 12:49 ` Mark Rutland [this message]
2023-01-04 14:31   ` [PATCH v2 1/3] ftrace: Maintain samples/ftrace Masami Hiramatsu
2023-01-03 12:49 ` [PATCH v2 2/3] ftrace: Export ftrace_free_filter() to modules Mark Rutland
2023-01-04 14:51   ` Masami Hiramatsu
2023-01-04 15:30     ` Mark Rutland
2023-01-04 16:03       ` Steven Rostedt
2023-01-03 12:49 ` [PATCH v2 3/3] ftrace: Add sample with custom ops Mark Rutland
2023-01-04 14:56   ` Masami Hiramatsu
2023-02-06 22:25   ` Guenter Roeck
2023-02-07  9:33     ` Mark Rutland

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=20230103124912.2948963-2-mark.rutland@arm.com \
    --to=mark.rutland@arm.com \
    --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 \
    /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