ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Thu, 28 Jul 2016 23:59:13 +0300	[thread overview]
Message-ID: <2443703.ScQNYO34Bz@avalon> (raw)
In-Reply-To: <20160728205324.GB5642@wfg-t540p.sh.intel.com>

Hi Fengguang,

On Friday 29 Jul 2016 04:53:24 Fengguang Wu wrote:
> On Thu, Jul 28, 2016 at 07:15:22PM +0300, Laurent Pinchart wrote:
> > On Wednesday 27 Jul 2016 22:50:27 Fengguang Wu 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.
> >>> 
> >>> 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.
> >> 
> >> Yeah sorry about that! There are many things that can impact 0-day
> >> system's stability: regressions, hard disk replacement, proxy issues,
> >> mailing list kicking off, vocations, etc. Which should improve over
> >> time as we add monitoring and self-test facilities. On the other hand,
> >> if you find such issues, please don't hesitate forwarding the error
> >> emails to us, so that we can check and take action quickly.
> >
> > There's no need to apologize, really. You've done and keep doing an
> > amazing work for which we're all thankful. The biggest problem I see that
> > would stop me from fully relying on 0-day is the lack of information about
> > such downtimes, leading me to wonder if the absence of a report really
> > means that everything is fine. A 0-day status page with information about
> > the current status and the planned downtime, as well as possibly the list
> > of trees covered by 0-day (I don't know whether part of that information
> > could be considered as confidential), would help a lot.
> 
> For that purpose you may subscribe to the BUILD SUCCESS notification
> by sending me an "opt-in" email with your tree URL.
> 
> That notification will be sent 1-2 hours after each branch's git push,
> which contains the build test progress on that branch. Based on which
> (or missing of it) you'll know if everything is on the track.

I know that such a feature exists, but I'm not sure all developers would 
appreciate the additional e-mail traffic. That's why I proposed a status page 
that could be polled when needed.

> This will actually turn that feature on for your tree:
> 
> https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/commit/?id=aa
> 0480dd8d58d234fdf0ff41bcb71a930aa024b9
> 
> commit aa0480dd8d58d234fdf0ff41bcb71a930aa024b9
> Author:     Fengguang Wu <fengguang.wu@intel.com>
> Commit:     Fengguang Wu <fengguang.wu@intel.com>
> CommitDate: Fri Jul 29 04:48:44 2016 +0800
> 
>     repo: notify build success for pinchartl-fbdev
> 
>     CC: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>     Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
>  repo/linux/pinchartl-fbdev | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/repo/linux/pinchartl-fbdev b/repo/linux/pinchartl-fbdev
> index bbb4dd1..cc6e19b 100644
> --- a/repo/linux/pinchartl-fbdev
> +++ b/repo/linux/pinchartl-fbdev
> @@ -1,5 +1,6 @@
>  url: git://linuxtv.org/pinchartl/fbdev.git
>  owner: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> +notify_build_success_branch: .*
>  subsystems:
>  - drm
>  - rcar-du

Thanks. I will actually deprecate that tree in favour of 
git://linuxtv.org/pinchartl/media.git :-) I'll send you a mail when that will 
be effective.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2016-07-28 20:59 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 [this message]
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=2443703.ScQNYO34Bz@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=fengguang.wu@intel.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