linux-trace-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
	"linux-trace-users@vger.kernel.org" 
	<linux-trace-users@vger.kernel.org>,
	Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Submit to the Tracing Microconference at Linux Plumbers 2019
Date: Wed, 10 Jul 2019 13:41:42 -0400	[thread overview]
Message-ID: <20190710134142.6aeafa38@gandalf.local.home> (raw)

Hi folks,

There will be a Tracing microconference this year at Linux Plumbers.
Linux Plumbers (https://linuxplumbersconf.org) will be held in Lisbon,
Portugal from September 9-11. The Tracing MC will be approximately a
four hour session focused on improving the Linux tracing infrastructure.

If there's a subject you would like to discuss at this microconference,
please submit a topic and abstract here:

  https://linuxplumbersconf.org/event/4/abstracts/

Select "Submit new proposal"

Fill out the title, the content and who will be leading the session,
then select the "Tracing MC topic" track and hit "Submit". Of course
you will also need to agree to follow the anti-harassment policy.

Remember, we are looking for discussions on improving tracing within
Linux. You can have up to 5 (maybe 7) minutes of presentation to bring
the audience up to speed with the issues at hand, but then the rest of
the time will be dedicated to discussion on how to solve and/or
implement the solution.

All submissions should be in by August 2, and I will hopefully be able
to decided what to discuss by August 9.

Even if you don't submit a topic, I hope to see you there to discuss
Linux tracing at Linux Plumbers in Lisbon.

Cheers,

-- Steve

                 reply	other threads:[~2019-07-10 17:41 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=20190710134142.6aeafa38@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=linux-trace-users@vger.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;
as well as URLs for NNTP newsgroup(s).