From: Andi Shyti <andi.shyti@linux.intel.com>
To: Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-gfx] [PATCH v2 0/2] Use i915 instead of dev_priv
Date: Fri, 21 Apr 2023 21:00:24 +0200 [thread overview]
Message-ID: <20230421190026.294208-1-andi.shyti@linux.intel.com> (raw)
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.
Thank you Andrzej and Rodrigo for your reviews.
Andi
Changelog
=========
v1 -> v2
- Fix double typo in the patch 1 commit:
/for_each_gt/for_each_engine/
- Phrase properly the commit of patch 2.
Andi Shyti (2):
drm/i915/i915_drv: Use proper parameter naming in for_each_engine()
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(-)
--
2.40.0
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH v2 0/2] Use i915 instead of dev_priv
Date: Fri, 21 Apr 2023 21:00:24 +0200 [thread overview]
Message-ID: <20230421190026.294208-1-andi.shyti@linux.intel.com> (raw)
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.
Thank you Andrzej and Rodrigo for your reviews.
Andi
Changelog
=========
v1 -> v2
- Fix double typo in the patch 1 commit:
/for_each_gt/for_each_engine/
- Phrase properly the commit of patch 2.
Andi Shyti (2):
drm/i915/i915_drv: Use proper parameter naming in for_each_engine()
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(-)
--
2.40.0
next reply other threads:[~2023-04-21 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 19:00 Andi Shyti [this message]
2023-04-21 19:00 ` [PATCH v2 0/2] Use i915 instead of dev_priv Andi Shyti
2023-04-21 19:00 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/i915_drv: Use proper parameter naming in for_each_engine() Andi Shyti
2023-04-21 19:00 ` Andi Shyti
2023-04-21 19:00 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/i915_drv: Use i915 instead of dev_priv insied the file_priv structure Andi Shyti
2023-04-21 19:00 ` Andi Shyti
2023-04-21 22:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use i915 instead of dev_priv (rev2) Patchwork
2023-04-21 22:29 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-21 22:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-22 9:43 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=20230421190026.294208-1-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.