I'm in favor of all Daniel said and my 2 cents here is just to
highlight how easy and straightforward is to create an intel-gpu-tools
testcase nowadays. If you know very well the feature you are
implementing you will spend couple of hours or 1 day maximum.
I agree with Daniel that it is difficult
On 10/30/2013 12:05 PM, Daniel Vetter wrote:
On Wed, Oct 30, 2013 at 7:11 PM, Ian Romanick wrote:
test coverage of the existing code _before_ starting a feature instead
of when the patches are ready for merging should help a lot, before
everyone is invested into patches already and mou
On Wed, Oct 30, 2013 at 7:11 PM, Ian Romanick wrote:
>> test coverage of the existing code _before_ starting a feature instead
>> of when the patches are ready for merging should help a lot, before
>> everyone is invested into patches already and mounting rebase pain looms
>> large.
>
> Th
On 10/30/2013 09:00 AM, Daniel Vetter wrote:
> [This is cross-posted to the public intel-gfx mailing list at
> http://lists.freedesktop.org/archives/intel-gfx/2013-October/035268.html
> I'll also present a quick overview of this at Gavin's kernel PDT next
> week.]
>
> Hi all,
>
> So in the past h
[This is cross-posted to the public intel-gfx mailing list at
http://lists.freedesktop.org/archives/intel-gfx/2013-October/035268.html
I'll also present a quick overview of this at Gavin's kernel PDT next week.]
Hi all,
So in the past half year we've had tons of sometimes rather heated
discus
