LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Paul Mackerras <paulus@samba.org>, Joe Perches <joe@perches.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] MAINTAINERS: Add arch/powerpc/kernel/trace to TRACING
Date: Thu, 24 Mar 2022 18:28:56 -0400	[thread overview]
Message-ID: <20220324182856.6f6a01d7@gandalf.local.home> (raw)
In-Reply-To: <8e2f707e2efa1fc1d1ffd2f9f6758e8c4a82c83e.1648132613.git.christophe.leroy@csgroup.eu>

On Thu, 24 Mar 2022 15:38:28 +0100
Christophe Leroy <christophe.leroy@csgroup.eu> wrote:

> diff --git a/MAINTAINERS b/MAINTAINERS
> index e127c2fb08a7..3b5943f34568 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19592,6 +19592,7 @@ T:	git git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
>  F:	Documentation/trace/ftrace.rst
>  F:	arch/*/*/*/ftrace.h
>  F:	arch/*/kernel/ftrace.c
> +F:	arch/powerpc/kernel/trace/

Perhaps replace the above two with:
   F:   arch/*/*/ftrace*
   F:   arch/*/*/*/ftrace*

As we also have things like ftrace_32.S, ftrace_64.S

Maybe even add:

   F: arch/*/*/*_ftrace.*
   F: arch/*/*/*/*_ftrace.*

to catch the "entry_ftrace.S" and friends (needing the leading "_" to not
get confused by any "bpftrace" files).

?

But in reality, I'm only a reviewer for ftrace in the archs. It really is
maintained by the arch maintainers. But it is still good that I get Cc'd on
any ftrace arch related changes.

-- Steve


>  F:	fs/tracefs/
>  F:	include/*/ftrace.h
>  F:	include/linux/trace*.h


      reply	other threads:[~2022-03-24 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 14:38 [PATCH] MAINTAINERS: Add arch/powerpc/kernel/trace to TRACING Christophe Leroy
2022-03-24 22:28 ` Steven Rostedt [this message]

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=20220324182856.6f6a01d7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.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