From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Mon, 25 Jul 2016 22:23:43 +0200 [thread overview]
Message-ID: <20160725202343.GJ11405@piout.net> (raw)
In-Reply-To: <20160725190125.GS5537@wotan.suse.de>
On 25/07/2016 at 21:01:25 +0200, Luis R. Rodriguez wrote :
>
> 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.
>
That's a good point.
> 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.
>
Well, I think it would also help to know how the patch/git tree
selection is done. Lately, I've been receiving less reports from 0-day
and some issues were found by Arnd's autobuilders after hitting
linux-next. I used to get report of compilation breakage 10-15 minutes
after the patch submission.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-25 20:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 19:01 [Ksummit-discuss] Nominating Fengguang Wu - 0-day Luis R. Rodriguez
2016-07-25 20:23 ` Alexandre Belloni [this message]
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=20160725202343.GJ11405@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mcgrof@suse.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 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.