From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/2] Use i915 instead of dev_priv
Date: Mon, 24 Apr 2023 13:38:26 +0300 [thread overview]
Message-ID: <87sfcp36ql.fsf@intel.com> (raw)
In-Reply-To: <ZER/u/tSEX8mXC7R@ashyti-mobl2.lan>
On Sun, 23 Apr 2023, Andi Shyti <andi.shyti@linux.intel.com> 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 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 i915_irq.h, which is a
>> bit tricky (but not much) as the "dev_priv" is hardcoded inside
>> some defines.
>>
>> Andi
>>
>> Andi Shyti (2):
>> drm/i915/i915_drv: Use proper parameter naming in for_each_gt()
>> drm/i915/i915_drv: Use i915 instead of dev_priv insied the file_priv
>> structure
>>
>> drivers/gpu/drm/i915/i915_drv.h | 462 ++++++++++++++++----------------
>> 1 file changed, 231 insertions(+), 231 deletions(-)
>
> Pushed to dmr-intel-gt-next.
That's going to create problems for us for weeks to come. I'm actually
tempted to ask Joonas or Tvrtko to just force push that out of there.
Only use drm-intel-gt-next for stuff that's specifically about gt or
gem, and touches files used by gt or gem only. For everything else, use
drm-intel-next. When in doubt, err on the side of drm-intel-next.
It's not enough that one of the patches changes parameters of
for_each_gt() macro.
We can cross-merge drm-intel-next to drm-intel-gt-next, but we can't
cross-merge drm-intel-gt-next to drm-intel-next. This means the only way
to sync those i915_drv.h changes to drm-intel-next is to have a
drm-intel-gt-next pull request merged to drm-next, and then backmerged
to drm-intel-next. That's not going to happen for several weeks.
Any change aimed at drm-intel-next that conflicts with the i915_drv.h
changes will now be pending on those merges.
BR,
Jani.
>
> Thanks Rodrigo and Andrzej for your review.
>
> Andi
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-04-24 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 13:46 [Intel-gfx] [PATCH 0/2] Use i915 instead of dev_priv Andi Shyti
2023-04-21 13:46 ` [Intel-gfx] [PATCH 1/2] drm/i915/i915_drv: Use proper parameter naming in for_each_gt() Andi Shyti
2023-04-21 14:00 ` Rodrigo Vivi
2023-04-21 14:05 ` Rodrigo Vivi
2023-04-21 14:37 ` Andi Shyti
2023-04-21 15:26 ` Andrzej Hajda
2023-04-21 13:46 ` [Intel-gfx] [PATCH 2/2] drm/i915/i915_drv: Use i915 instead of dev_priv insied the file_priv structure Andi Shyti
2023-04-21 14:07 ` Rodrigo Vivi
2023-04-21 14:51 ` Andi Shyti
2023-04-21 15:27 ` Andrzej Hajda
2023-04-21 15:19 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use i915 instead of dev_priv Patchwork
2023-04-21 15:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-23 0:45 ` [Intel-gfx] [PATCH 0/2] " Andi Shyti
2023-04-24 10:38 ` Jani Nikula [this message]
2023-04-24 14:32 ` Andi Shyti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfcp36ql.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox