All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Saarinen, Jani" <jani.saarinen@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ Fi.CI.BAT: warning for series starting with [1/2] drm/i915: Pre-calculate engine context size
Date: Wed, 26 Apr 2017 12:43:18 +0000	[thread overview]
Message-ID: <43D4F724E12AB6478FC1572B3FBE89D04C34B2D0@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <1493210188.4179.14.camel@linux.intel.com>

Hi, 
> -----Original Message-----
> From: Joonas Lahtinen [mailto:joonas.lahtinen@linux.intel.com]
> Sent: Wednesday, April 26, 2017 3:36 PM
> To: Saarinen, Jani <jani.saarinen@intel.com>; intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [1/2]
> drm/i915: Pre-calculate engine context size
> 
> On ke, 2017-04-26 at 10:43 +0000, Saarinen, Jani wrote:
> > >
> > > -----Original Message-----
> > > Subject: [Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [1/2]
> drm/i915:
> > > Pre-calculate engine context size
> > >
> > > == Series Details ==
> > >
> > > Series: series starting with [1/2] drm/i915: Pre-calculate engine
> > > context size URL   : https://patchwork.freedesktop.org/series/23559/
> > > State : warning
> > >
> > > == Summary ==
> > >
> > > Series 23559v1 Series without cover letter
> > > https://patchwork.freedesktop.org/api/1.0/series/23559/revisions/1/m
> > > box/
> > >
> >
> > How about trybot first?
> 
> What exactly is the point of running CI on intel-gfx traffic if everything is
> supposed to be sent to trybot first? Sending trivial series to trybot first would
> double the already untolerable latency of the system. intel-gfx is supposed to be
Well I am thinking that first most obvious failures are caught by trybot and when 
passing there then sending for review, this is what eg. Chris is doing a lot. 
So that trybot serves developers pre-pre-criteria. 
But agree there is latency is there are work in the queue but not if drm, dif, dinf and pw and clean,
then is just matter of 10+ minutes. 

> a place to discuss the patches among the developers, or you think we should
> have intel-gfx-dev for that and everything but ready-to-merge series are sent
> there?
Well it is up to developers to decide, just saying that if patches are totally bogus, maybe test first 
not on the list but try-bot list ;)

> 
> Regards, Joonas
> --

Jani Saarinen
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-04-26 12:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  9:11 [PATCH 1/2] drm/i915: Pre-calculate engine context size Joonas Lahtinen
2017-04-26  9:10 ` Zhi Wang
2017-04-26  9:52   ` Joonas Lahtinen
2017-04-26  9:47     ` About the context image size on GEN8+ Zhi Wang
2017-04-26  9:57     ` [PATCH 1/2] drm/i915: Pre-calculate engine context size Zhi Wang
2017-04-26 16:20       ` Daniele Ceraolo Spurio
2017-04-27  2:11         ` Zhi Wang
2017-04-26  9:11 ` [PATCH 2/2] drm/i915: Sanitize hardware context computation Joonas Lahtinen
2017-04-26  9:36 ` [PATCH 1/2] drm/i915: Pre-calculate engine context size Chris Wilson
2017-04-26  9:43 ` ✗ Fi.CI.BAT: warning for series starting with [1/2] " Patchwork
2017-04-26 10:43   ` Saarinen, Jani
2017-04-26 12:36     ` Joonas Lahtinen
2017-04-26 12:43       ` Saarinen, Jani [this message]
2017-04-26 13:04         ` Chris Wilson

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=43D4F724E12AB6478FC1572B3FBE89D04C34B2D0@IRSMSX106.ger.corp.intel.com \
    --to=jani.saarinen@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.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.