From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Beau Belgrave <beaub@linux.microsoft.com>,
linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@kernel.org>,
Tom Zanussi <zanussi@kernel.org>
Subject: Re: [PATCH 4/5] libtraceevent: Add __rel_loc relative location attribute support
Date: Wed, 17 Nov 2021 10:14:47 -0500 [thread overview]
Message-ID: <20211117101447.39a394d4@gandalf.local.home> (raw)
In-Reply-To: <20211117233317.841b81fa8b709455b7df9da6@kernel.org>
On Wed, 17 Nov 2021 23:33:17 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > Care to send a patch against:
> >
> > https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
> >
> > And Cc linux-trace-devel@vger.kernel.org
>
> Should I cc to LKML too?
Only if you want to, but it is not necessary. Patches to linux-trace-devel
end up at:
https://patchwork.kernel.org/project/linux-trace-devel/list/
-- Steve
next prev parent reply other threads:[~2021-11-17 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 10:19 [PATCH 0/5] tracing: Add __rel_loc support Masami Hiramatsu
2021-11-15 10:20 ` [PATCH 1/5] tracing: Support __rel_loc relative dynamic data location attribute Masami Hiramatsu
2021-11-15 10:20 ` [PATCH 2/5] tracing: Add '__rel_loc' using trace event macros Masami Hiramatsu
2021-11-15 10:20 ` [PATCH 3/5] samples/trace_event: Add '__rel_loc' using sample event Masami Hiramatsu
2021-11-15 10:20 ` [PATCH 4/5] libtraceevent: Add __rel_loc relative location attribute support Masami Hiramatsu
2021-11-16 22:23 ` Steven Rostedt
2021-11-17 14:33 ` Masami Hiramatsu
2021-11-17 15:14 ` Steven Rostedt [this message]
2021-11-22 5:05 ` Masami Hiramatsu
2021-11-22 16:25 ` Steven Rostedt
2021-11-23 12:07 ` Masami Hiramatsu
2021-11-15 10:20 ` [PATCH 5/5] tools/perf: Add __rel_loc support Masami Hiramatsu
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=20211117101447.39a394d4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=beaub@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=zanussi@kernel.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
all inboxes | Powered by JetHome®