From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
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: Wed, 1 Jul 2020 13:50:02 +0200 [thread overview]
Message-ID: <CAKXUXMzfnVw_SMbuO7z=+M0LS3kv92Aqw5ZkKZEEK9BwnFQCsQ@mail.gmail.com> (raw)
In-Reply-To: <20200201190222.GC13359@kernel.org>
On Sat, Feb 1, 2020 at 8:02 PM Arnaldo Carvalho de Melo
<arnaldo.melo@gmail.com> wrote:
>
> Em Sat, Feb 01, 2020 at 01:14:53PM -0500, Steven Rostedt escreveu:
> > On Sat, 1 Feb 2020 17:19:31 +0100
> > 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.
> >
> > Thanks Lukas!
> >
> > Arnaldo, would you like to take this?
> >
> > Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>
> Sure
>
Arnaldo, I think you never picked this patch and it did not make it
into mainline. I checked that the patch still applies to the current
master, so maybe you can pick it now. It is a minor non-urgent patch
and cannot break any builds :)
Thanks,
Lukas
next prev parent reply other threads:[~2020-07-01 11:50 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 [this message]
2020-02-02 6:42 ` Tzvetomir Stoyanov
2020-02-03 10:23 ` Andy Shevchenko
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='CAKXUXMzfnVw_SMbuO7z=+M0LS3kv92Aqw5ZkKZEEK9BwnFQCsQ@mail.gmail.com' \
--to=lukas.bulwahn@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).