[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220324182856.6f6a01d7@gandalf.local.home>
Date:   Thu, 24 Mar 2022 18:28:56 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Christophe Leroy <christophe.leroy@...roup.eu>
Cc:     Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Paul Mackerras <paulus@...ba.org>,
        Michael Ellerman <mpe@...erman.id.au>,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        linuxppc-dev@...ts.ozlabs.org, Joe Perches <joe@...ches.com>
Subject: Re: [PATCH] MAINTAINERS: Add arch/powerpc/kernel/trace to TRACING
On Thu, 24 Mar 2022 15:38:28 +0100
Christophe Leroy <christophe.leroy@...roup.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
Powered by blists - more mailing lists
 
