From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Mon, 25 Jul 2016 21:01:25 +0200 [thread overview]
Message-ID: <20160725190125.GS5537@wotan.suse.de> (raw)
It surprises Fengguang Wu <fengguang.wu@intel.com> hasn't been nominated yet,
so I'd like to nominate him. The mechanical process should probably include in
the future a scrape for top Reported-by contributors.
Fengguang's 0-day infrastructure is invaluable to day to day kernel
development, having him present would be great for any questions that may come
up. Getting a statistical overview / update of impact / any major architectural
changes of the 0-day infrastructure would also be very useful. If maintainers
are not yet using 0-day it would be great to hear why. If your contributors are
not using 0-day (I know some of you exist) I'd like to know why you don't use it,
I often run into issues on linux-next which at times I have to fix, if 0-day
would have been used a folowup fix would not have been needed.
Luis
next reply other threads:[~2016-07-25 19:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 19:01 Luis R. Rodriguez [this message]
2016-07-25 20:23 ` [Ksummit-discuss] Nominating Fengguang Wu - 0-day Alexandre Belloni
2016-07-26 3:10 ` Vinod Koul
2016-07-26 8:16 ` Laurent Pinchart
2016-07-26 8:56 ` Vinod Koul
2016-07-28 13:20 ` Fengguang Wu
2016-07-27 14:50 ` Fengguang Wu
2016-07-28 16:15 ` Laurent Pinchart
2016-07-28 20:53 ` Fengguang Wu
2016-07-28 20:59 ` Laurent Pinchart
2016-07-28 22:38 ` Dmitry Torokhov
2016-07-29 16:26 ` Vinod Koul
2016-07-28 23:07 ` Fengguang Wu
2016-07-28 23:33 ` Luis R. Rodriguez
2016-07-29 0:09 ` Fengguang Wu
2016-07-29 15:12 ` Bjorn Helgaas
2016-07-30 17:05 ` Luis R. Rodriguez
2016-07-30 17:24 ` Guenter Roeck
2016-07-31 6:35 ` Fengguang Wu
2016-07-31 17:32 ` Vinod Koul
2016-08-01 13:35 ` Fengguang Wu
2016-07-28 23:38 ` Jiri Kosina
2016-07-31 11:16 ` Fengguang Wu
2016-07-29 2:00 ` Steven Rostedt
2016-07-29 2:26 ` Fengguang Wu
2016-07-27 14:41 ` Fengguang Wu
2016-07-28 17:15 ` Guenter Roeck
2016-07-28 17:21 ` Dmitry Vyukov
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=20160725190125.GS5537@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=ksummit-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 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.