On Tue, Apr 12, 2016 at 12:52:24PM +0100, Peter Antoine wrote:
> Chris,
>
> If the test is ok, can you review-by this patch.
Yup, my box decided that was good time to suffer fs corruption. Patched
up and resent for CI with my r-b.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
Chris,
If the test is ok, can you review-by this patch.
Thanks,
Peter.
On Tue, 22 Mar 2016, Peter Antoine wrote:
Chris.
Can these patches be reviewed without the tests or are they blocked waiting
for the tests.
Are the patches acceptable?
Thanks,
Peter.
On Tue, 15 Mar 2016, Peter
On Tue, Mar 22, 2016 at 09:02:17AM +, Peter Antoine wrote:
> Chris.
>
> Can these patches be reviewed without the tests or are they blocked
> waiting for the tests.
More or less waiting upon the tests. Or where is the bugzilla?
It would only take a couple of hours to write something like:
Chris.
Can these patches be reviewed without the tests or are they blocked
waiting for the tests.
Are the patches acceptable?
Thanks,
Peter.
On Tue, 15 Mar 2016, Peter Antoine wrote:
Chris,
Testcases are underway, validation are working on them.
Peter.
On Tue, 15 Mar 2016, Chris Wilson
Chris,
Testcases are underway, validation are working on them.
Peter.
On Tue, 15 Mar 2016, Chris Wilson wrote:
On Mon, Mar 14, 2016 at 03:11:02PM +, Peter Antoine wrote:
Allow for the MOCS to be programmed for all engines.
Currently we program the MOCS when the first render batch
goes
On Mon, Mar 14, 2016 at 03:11:02PM +, Peter Antoine wrote:
> Allow for the MOCS to be programmed for all engines.
> Currently we program the MOCS when the first render batch
> goes through. This works on most platforms but fails on
> platforms that do not run a render batch early,
> i.e.
Allow for the MOCS to be programmed for all engines.
Currently we program the MOCS when the first render batch
goes through. This works on most platforms but fails on
platforms that do not run a render batch early,
i.e. headless servers. The patch now programs all initialised engines
on init and
