From: Steven Rostedt <rostedt@goodmis.org>
To: tech-board-discuss@lists.linuxfoundation.org,
ksummit-discuss@lists.linuxfoundation.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [Ksummit-discuss] TAB nomination for Steven Rostedt
Date: Tue, 27 Aug 2019 22:19:38 -0400 [thread overview]
Message-ID: <20190827221938.0552eacb@oasis.local.home> (raw)
I would like to nominate myself, Steven Rostedt, for election to the
Linux Foundation Technical Advisory Board (TAB).
Candidate statement:
I have been highly involved with the Linux kernel community since 2004,
as a developer, a user, maintainer and educator. When I first came onto
the board, my platform was to help bridge various parts of the Linux
ecosystem. I've been working to help developers reach across their
realms of expertise and unite with other developers in order to have
better integration of the tools within the GNU and Linux systems. Being
part of the advisory board to the Linux Foundation has facilitate this
goal. I am also on the planning committee for Linux Plumbers and have
become the Microconference Chair. As such I have succeeded in bringing
in developers to host a Database microconference for the first time at
Plumbers. The combination of being both on the TAB as well as a
Plumbers committee member has be extremely useful in my goal of
bringing all those that interact with Linux closer together. I would
like to continue this work for at least one more term.
Little more about me:
I'm one of the original developers of the PREEMPT_RT patch (which looks
to finally be merged into mainline). I'm the original author and
current maintainer of Ftrace, the official tracer of the Linux kernel.
I've created ktest.pl that lives in the kernel proper under the tools
directory which is a testing framework that was written to help
developers run their own tests. I'm also the one that added "make
localmodconfig" that brings your kernel compile time down tremendously!
-- Steve
reply other threads:[~2019-08-28 2:19 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=20190827221938.0552eacb@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).