From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org,
linux-doc@vger.kernel.org, Juri Lelli <juri.lelli@redhat.com>,
William White <chwhite@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH V2 0/9] rtla improvements
Date: Mon, 29 May 2023 10:38:16 +0200 [thread overview]
Message-ID: <838075fb-8b82-1aee-97a1-95102c03c16d@kernel.org> (raw)
In-Reply-To: <20230529042839.5d4af427@rorschach.local.home>
On 5/29/23 10:28, Steven Rostedt wrote:
> Hi Daniel,
>
> Could you make sure to Cc linux-trace-kernel@vger.kernel.org and not
> linux-trace-devel. The former is for any patch that goes into the
> kernel repo, the later is for the tracing libraries (like libtracefs).
> The reason why this matters is that the patchwork that is associated to
> the Linux kernel tree will not get these (and I will not work on them
> when I'm working on kernel patches). But it will go into the
> patchwork for the libraries (and never be processed by the patchwork
> infrastructure), and I will likely not work on them, because when I
> look at the library patchwork, I ignore anything that goes into the
> kernel.
Sure, I will do that. IIRC, we agreed that we would use linux-trace-devel for
rtla because it is a user-space tool. But I agree with you, as they are patches
going to the kernel repo, linux-trace-kernel is a better place. It is easier to
myself too... :-).
>
> Perhaps resend with the proper Cc and it will then be processed. I
> allowed this to happen before, but that's because I did everything
> manually and not with my scripts. And I'm tired of doing that.
I will do that in the v3.
I will also update the maintainers entry for RTLA and RV, as both are pointing to
linux-trace-devel.
Thanks!
-- Daniel
>
> Thanks,
>
> -- Steve
next prev parent reply other threads:[~2023-05-29 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 17:44 [PATCH V2 0/9] rtla improvements Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 1/9] rtla: Add -C cgroup support Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 2/9] rtla: Add --house-keeping option Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 3/9] rtla: Change monitored_cpus from char * to cpu_set_t Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 4/9] rtla: Automatically move rtla to a house-keeping cpu Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 5/9] rtla/timerlat: Give timerlat auto analysis its own instance Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 6/9] rtla/timerlat_hist: Add auto-analysis support Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 7/9] rtla: Start the tracers after creating all instances Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 8/9] rtla/hwnoise: Reduce runtime to 75% Daniel Bristot de Oliveira
2023-05-23 17:44 ` [PATCH V2 9/9] rtla: Add timerlat user-space support for timerlat top Daniel Bristot de Oliveira
2023-05-29 8:28 ` [PATCH V2 0/9] rtla improvements Steven Rostedt
2023-05-29 8:38 ` Daniel Bristot de Oliveira [this message]
2023-05-29 8:43 ` Steven Rostedt
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=838075fb-8b82-1aee-97a1-95102c03c16d@kernel.org \
--to=bristot@kernel.org \
--cc=chwhite@redhat.com \
--cc=corbet@lwn.net \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhiramat@kernel.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;
as well as URLs for NNTP newsgroup(s).