Re: [PATCH 0/2] Use i915 instead of dev_priv

Hi Jani, > >> just another "Friday patch". While reviewing some patches from > >> Tejas I found a bit confusing the use of dev_priv__ inside the > >> for_each_engine(), perhaps it should be moved inside the gt/? > >> > >> As I was at it I made the /dev_priv/i915/ change which is still > >> harmle

Re: [PATCH 0/2] Use i915 instead of dev_priv

On Sun, 23 Apr 2023, Andi Shyti wrote: > Hi, > > On Fri, Apr 21, 2023 at 03:46:52PM +0200, Andi Shyti wrote: >> Hi, >> >> just another "Friday patch". While reviewing some patches from >> Tejas I found a bit confusing the use of dev_priv__ inside the >> for_each_engine(), perhaps it should be mov

Re: [PATCH 0/2] Use i915 instead of dev_priv

Hi, On Fri, Apr 21, 2023 at 03:46:52PM +0200, Andi Shyti wrote: > Hi, > > just another "Friday patch". While reviewing some patches from > Tejas I found a bit confusing the use of dev_priv__ inside the > for_each_engine(), perhaps it should be moved inside the gt/? > > As I was at it I made the

[PATCH 0/2] Use i915 instead of dev_priv

Hi, just another "Friday patch". While reviewing some patches from Tejas I found a bit confusing the use of dev_priv__ inside the for_each_engine(), perhaps it should be moved inside the gt/? As I was at it I made the /dev_priv/i915/ change which is still harmless. Next in queue is to change the