From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-trace-devel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] MAINTAINERS: add TRACE EVENT LIBRARY section
Date: Mon, 3 Feb 2020 12:23:44 +0200 [thread overview]
Message-ID: <CAHp75VezYub1YzGSMrwQ7ntAV6EftgLxFiQu9wVnekPHPe4d_g@mail.gmail.com> (raw)
In-Reply-To: <20200201161931.29665-1-lukas.bulwahn@gmail.com>
On Sat, Feb 1, 2020 at 6:21 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> The git history shows that the files under ./tools/lib/traceevent/ are
> being developed and maintained by Tzetomir Stoyanov and Steven Rostedt
> and are discussed on the linux-trace-devel list.
>
> Add a suitable section in MAINTAINERS for patches to reach them.
>
> This was identified with a small script that finds all files only
> belonging to "THE REST" according to the current MAINTAINERS file, and I
> acted upon its output.
> +TRACE EVENT LIBRARY
> +M: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
> +M: Steven Rostedt <rostedt@goodmis.org>
> +L: linux-trace-devel@vger.kernel.org
> +S: Maintained
> +F: tools/lib/traceevent/
Don't forget to run early mentioned scripts (in some other threads).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-02-03 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 16:19 [PATCH RFC] MAINTAINERS: add TRACE EVENT LIBRARY section Lukas Bulwahn
2020-02-01 18:14 ` Steven Rostedt
2020-02-01 19:02 ` Arnaldo Carvalho de Melo
2020-07-01 11:50 ` Lukas Bulwahn
2020-02-02 6:42 ` Tzvetomir Stoyanov
2020-02-03 10:23 ` Andy Shevchenko [this message]
2020-02-04 4:41 ` Lukas Bulwahn
2020-02-04 11:12 ` Andy Shevchenko
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=CAHp75VezYub1YzGSMrwQ7ntAV6EftgLxFiQu9wVnekPHPe4d_g@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tz.stoyanov@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.