From: Fengguang Wu <fengguang.wu@intel.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Wed, 27 Jul 2016 22:41:14 +0800 [thread overview]
Message-ID: <20160727144114.GA2273@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160725190125.GS5537@wotan.suse.de>
On Mon, Jul 25, 2016 at 09:01:25PM +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.
Thanks for your appreciations, Luis!
>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.
I'd be glad to answer questions and more importantly, collect
feedbacks on where and how to improve the 0-day infrastructure.
There are 2 major parts in 0-day: build tests and runtime tests.
While build tests will be continuously improved, there may be a lot
more to be desired for runtime tests, which should be my main focus
in the coming year.
>Getting a statistical overview / update of impact / any major architectural
>changes of the 0-day infrastructure would also be very useful.
Sure if there are interests.
>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.
0-day tries to monitor as many git trees as possible, so that fresh
code can be tested before they land maintainer trees and linux-next.
To achieve better early code coverage, we periodically check if there
are new git trees showing up in git.kernel.org, in mainline git log
or mentioned in LKML emails. And add the newly discovered ones
unsolicited. :)
That said, it's still possible errors hit linux-next. Sometimes it may
be due to bug in 0-day or temporarily out of service. The solution
would be to improve 0-day system's stability and add more self-tests
to the system. Quick feedbacks about build/boot errors missed by 0-day
would also be highly appreciated.
Thanks,
Fengguang
next prev parent reply other threads:[~2016-07-27 14:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 19:01 Luis R. Rodriguez
2016-07-25 20:23 ` 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 [this message]
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=20160727144114.GA2273@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox