From: Steven Rostedt <rostedt@goodmis.org>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] TAB Nomination
Date: Mon, 12 Nov 2018 23:31:53 -0500 [thread overview]
Message-ID: <20181112233153.420e4fa3@vmware.local.home> (raw)
In-Reply-To: <20181113014631.7cf11233@silica.lan>
On Tue, 13 Nov 2018 01:46:31 -0200
Mauro Carvalho Chehab <mchehab@kernel.org> wrote:
> Hi,
>
> I've been actively working at the Linux Kernel since 2005, not only as a
> developer but also maintaining the Media subsystem with due care. At the
> time I started doing it, on my spare time, we started with about 30 patches
> merged per Kernel release, having a consistent sustainable grow along this
> time. We have now about 400-500 patches per merge window, being one of the
> most active development community. I also didn't miss a single merge window.
Hi Mauro,
I added you to the Google Doc, but it may be too late to get added to
the slide show.
-- Steve
next prev parent reply other threads:[~2018-11-13 4:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 3:46 [Ksummit-discuss] TAB Nomination Mauro Carvalho Chehab
2018-11-13 4:31 ` Steven Rostedt [this message]
2018-11-13 4:48 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 6:12 [Ksummit-discuss] TAB nomination Andy Lutomirski
2018-11-13 6:58 ` Steven Rostedt
2018-11-13 7:09 ` Andy Lutomirski
2018-11-13 19:06 ` Chris Mason
2018-11-12 20:09 Laurent Pinchart
2018-11-10 20:52 [Ksummit-discuss] TAB Nomination Dan Williams
2018-11-10 18:44 Laura Abbott
2018-11-08 5:14 [Ksummit-discuss] TAB nomination Kees Cook
2018-11-07 16:54 Shuah Khan
2018-11-04 17:12 Linux Foundation Technical Advisory Board Elections -- Call for nominations Chris Mason
2018-11-06 23:42 ` [Ksummit-discuss] TAB nomination Olof Johansson
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=20181112233153.420e4fa3@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.