From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Yordan Karadzhov <y.karadz@gmail.com>,
Slavomir Kaslev <kaslevs@vmware.com>,
Tzvetomir Stoyanov <tstoyanov@vmware.com>,
Matt Helsley <mhelsley@vmware.com>
Subject: Patchwork is live for linux-trace-devel!
Date: Fri, 11 Jan 2019 17:12:10 -0500 [thread overview]
Message-ID: <20190111171210.13e83e4b@gandalf.local.home> (raw)
FYI, we now have patchwork working for linux-trace-devel, and it's
also archived. Now I don't need to use my INBOX to figure out what I
need to handle for trace-cmd and KernelShark.
https://patchwork.kernel.org/project/linux-trace-devel/list/
And the lists are archived here:
https://lore.kernel.org/linux-trace-devel/
https://lore.kernel.org/linux-trace-users/
-- Steve
reply other threads:[~2019-01-11 22:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190111171210.13e83e4b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kaslevs@vmware.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mhelsley@vmware.com \
--cc=tstoyanov@vmware.com \
--cc=y.karadz@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).