ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Tue, 26 Jul 2016 11:16:40 +0300	[thread overview]
Message-ID: <1781582.RPTOZ0rvdq@avalon> (raw)
In-Reply-To: <20160726031007.GH9681@localhost>

Hello,

On Tuesday 26 Jul 2016 08:40:07 Vinod Koul wrote:
> On Mon, Jul 25, 2016 at 10:23:43PM +0200, Alexandre Belloni wrote:
> > 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.
> 
> I am using it a lot :)
> 
> > 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.

I second that. 0-day is an amazing tool, but relying on it requires developers 
to trust that the tool will perform its job as expected. A proper 
understanding of the logic behind patch/git tree selection would be very 
valuable, as well as how the build bot handles its 500+ kernel configurations.

Even though 0-day is an external tool, maybe it deserves an entry in 
Documentation/ ? A public web page hosting the list of all git registered git 
trees could be useful too.

> Pls check if the mailing list is still subscribed. I had the same issue
> and found that his ID was kicked off from the list, which is quite
> typical w/ Intel accounts & vger.
> 
> Since work is done by scripts, people may not have noticed.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2016-07-26  8:16 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 [this message]
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=1781582.RPTOZ0rvdq@avalon \
    --to=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox