[Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, Chris) - Make sure the mock engine name is null-terminated (Tvrtko, Chris) v3: Because I'm stupid (Chris) v4: Verify engine name wasn't

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On 04/07/2017 10:11 AM, Chris Wilson wrote: On Fri, Apr 07, 2017 at 06:23:14PM +0200, Michal Wajdeczko wrote: On Fri, Apr 07, 2017 at 02:15:47AM -0700, Oscar Mateo wrote: Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On Fri, Apr 07, 2017 at 06:23:14PM +0200, Michal Wajdeczko wrote: > On Fri, Apr 07, 2017 at 02:15:47AM -0700, Oscar Mateo wrote: > > Not really needed, but makes the next change a little bit more compact. > > > > v2: > > - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, >

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On Fri, Apr 07, 2017 at 02:15:47AM -0700, Oscar Mateo wrote: > Not really needed, but makes the next change a little bit more compact. > > v2: > - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, > Chris) > - Make sure the mock engine name is null-terminated (Tvrtko,

[Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, Chris) - Make sure the mock engine name is null-terminated (Tvrtko, Chris) v3: Because I'm stupid (Chris) v4: Verify engine name wasn't

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On Thu, Apr 06, 2017 at 08:00:14AM -0700, Oscar Mateo wrote: > Not really needed, but makes the next change a little bit more compact. > > v2: > - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, > Chris) > - Make sure the mock engine name is null-terminated (Tvrtko,

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On 06/04/2017 16:00, Oscar Mateo wrote: Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, Chris) - Make sure the mock engine name is null-terminated (Tvrtko, Chris) v3: Because I'm stupid

[Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, Chris) - Make sure the mock engine name is null-terminated (Tvrtko, Chris) v3: Because I'm stupid (Chris) Cc: Tvrtko Ursulin

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On 04/06/2017 01:10 PM, Chris Wilson wrote: On Thu, Apr 06, 2017 at 05:55:42AM -0700, Oscar Mateo wrote: Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, Chris) - Make sure the mock

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On Thu, Apr 06, 2017 at 05:55:42AM -0700, Oscar Mateo wrote: > Not really needed, but makes the next change a little bit more compact. > > v2: > - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, > Chris) > - Make sure the mock engine name is null-terminated (Tvrtko,

[Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

Not really needed, but makes the next change a little bit more compact. v2: - Use zero-based numbering for engine names: xcs0, xcs1.. xcsN (Tvrtko, Chris) - Make sure the mock engine name is null-terminated (Tvrtko, Chris) Cc: Tvrtko Ursulin Cc: Paulo Zanoni

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On Thu, Apr 06, 2017 at 07:37:20PM +0100, Tvrtko Ursulin wrote: > > On 06/04/2017 12:22, Oscar Mateo wrote: > >On 04/06/2017 11:02 AM, Tvrtko Ursulin wrote: > >>On 05/04/2017 10:30, Oscar Mateo wrote: > >>>Not really needed, but makes the next change a little bit more compact. > >>> > >>>Cc:

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On 06/04/2017 12:22, Oscar Mateo wrote: On 04/06/2017 11:02 AM, Tvrtko Ursulin wrote: On 05/04/2017 10:30, Oscar Mateo wrote: Not really needed, but makes the next change a little bit more compact. Cc: Tvrtko Ursulin Cc: Paulo Zanoni Cc:

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On 04/06/2017 11:02 AM, Tvrtko Ursulin wrote: On 05/04/2017 10:30, Oscar Mateo wrote: Not really needed, but makes the next change a little bit more compact. Cc: Tvrtko Ursulin Cc: Paulo Zanoni Cc: Rodrigo Vivi

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On Thu, Apr 06, 2017 at 07:02:10PM +0100, Tvrtko Ursulin wrote: > > On 05/04/2017 10:30, Oscar Mateo wrote: > >@@ -100,6 +100,7 @@ > > { > > const struct engine_info *info = _engines[id]; > > struct intel_engine_cs *engine; > >+char instance[3] = ""; > > > >

Re: [Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

On 05/04/2017 10:30, Oscar Mateo wrote: Not really needed, but makes the next change a little bit more compact. Cc: Tvrtko Ursulin Cc: Paulo Zanoni Cc: Rodrigo Vivi Cc: Chris Wilson Cc:

[Intel-gfx] [PATCH 3/5] drm/i915: Generate the engine name based on the instance number

Not really needed, but makes the next change a little bit more compact. Cc: Tvrtko Ursulin Cc: Paulo Zanoni Cc: Rodrigo Vivi Cc: Chris Wilson Cc: Daniele Ceraolo Spurio