On to, 2016-02-25 at 08:48 -0800, Matt Roper wrote:
> I never got a CI email for this (probably because fdo was down for a
> while),
> but I can see the results below in patchwork
We also have the problem, that if a patch prevents a machine from
booting that machine won't be included in the CI
On Mon, Feb 29, 2016 at 09:23:14AM +0100, Maarten Lankhorst wrote:
> Op 25-02-16 om 17:48 schreef Matt Roper:
> > I never got a CI email for this (probably because fdo was down for a while),
> > but I can see the results below in patchwork
> >
> >> Test gem_cs_prefetch:
> >> Subgroup
Op 25-02-16 om 17:48 schreef Matt Roper:
> I never got a CI email for this (probably because fdo was down for a while),
> but I can see the results below in patchwork
>
>> Test gem_cs_prefetch:
>> Subgroup basic-default:
>> incomplete -> PASS (ilk-hp8440p)
>> Test
I never got a CI email for this (probably because fdo was down for a while),
but I can see the results below in patchwork
> Test gem_cs_prefetch:
> Subgroup basic-default:
> incomplete -> PASS (ilk-hp8440p)
> Test kms_flip:
> Subgroup basic-flip-vs-dpms:
Op 24-02-16 om 02:24 schreef Matt Roper:
> On Tue, Feb 23, 2016 at 05:20:13PM -0800, Matt Roper wrote:
>> In addition to calculating final watermarks, let's also pre-calculate a
>> set of intermediate watermark values at atomic check time. These
>> intermediate watermarks are a combination of the
On Tue, Feb 23, 2016 at 05:20:13PM -0800, Matt Roper wrote:
> In addition to calculating final watermarks, let's also pre-calculate a
> set of intermediate watermark values at atomic check time. These
> intermediate watermarks are a combination of the watermarks for the old
> state and the new
In addition to calculating final watermarks, let's also pre-calculate a
set of intermediate watermark values at atomic check time. These
intermediate watermarks are a combination of the watermarks for the old
state and the new state; they should satisfy the requirements of both
states which means
