From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Sarvela, Tomi P" <tomi.p.sarvela@intel.com>,
intel-gfx@lists.freedesktop.org, shashidhar.hiremath@intel.com
Subject: Re: [PATCH v8 1/1] drm/i915/bxt: Check BIOS RC6 setup before enabling RC6
Date: Mon, 15 Feb 2016 18:07:47 +0100 [thread overview]
Message-ID: <20160215170747.GY11240@phenom.ffwll.local> (raw)
In-Reply-To: <8737t3w88c.fsf@intel.com>
On Mon, Feb 08, 2016 at 05:08:03PM +0200, Jani Nikula wrote:
> On Mon, 08 Feb 2016, Imre Deak <imre.deak@intel.com> wrote:
> >> > Thanks for the patch, I pushed it to -dinq.
> >>
> >> The rule is, we should wait for the CI results before pushing.
> >
> > Yes, I forgot to wait for the result for this version of the patch,
> > thanks for pointing it out. As a side-note the CI result still didn't
> > show up, what to do in that case? Resend the patch after a day or so?
>
> Complain to Damien and/or Tomi.
CI is/was down. Please don't push patches when that happens, but instead
wait for things to stabilize again. Yes that slows things down, but otoh
everytime CI is down we manage to sneak in an overlapping regression. And
recovering from overlapping regressions makes everything even more painful
than it already is.
Yes, some kind of CI status dashboard is on the wishlist.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-15 17:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1454531039.12879.4.camel@intel.com>
2016-02-05 18:43 ` [PATCH v8 1/1] drm/i915/bxt: Check BIOS RC6 setup before enabling RC6 Sagar Arun Kamble
2016-02-05 21:38 ` Imre Deak
2016-02-08 9:19 ` Jani Nikula
2016-02-08 14:18 ` Imre Deak
2016-02-08 15:08 ` Jani Nikula
2016-02-15 17:07 ` Daniel Vetter [this message]
2016-02-16 7:52 ` Tomi Sarvela
2016-02-16 15:28 ` Daniel Vetter
2016-02-16 15:45 ` Tomi Sarvela
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=20160215170747.GY11240@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=shashidhar.hiremath@intel.com \
--cc=tomi.p.sarvela@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox