From: Jani Nikula <jani.nikula@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: lucas.demarchi@intel.com, Gustavo Sousa <gustavo.sousa@intel.com>,
jani.nikula@intel.com
Subject: [PATCH 0/3] drm/xe: drvdata cleanups
Date: Mon, 12 Aug 2024 13:30:18 +0300 [thread overview]
Message-ID: <cover.1723458544.git.jani.nikula@intel.com> (raw)
The first patches from [1] just for xe, to be merged via drm-xe-next.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/136621/
Jani Nikula (3):
drm/xe/tests: remove unused leftover xe_call_for_each_device()
drm/xe: use pdev_to_xe_device() instead of pci_get_drvdata() directly
drm/xe: add kdev_to_xe_device() helper and use it
drivers/gpu/drm/xe/tests/xe_pci.c | 52 --------------------------
drivers/gpu/drm/xe/tests/xe_pci_test.h | 1 -
drivers/gpu/drm/xe/xe_device.h | 5 +++
drivers/gpu/drm/xe/xe_gsc_proxy.c | 9 +----
drivers/gpu/drm/xe/xe_pci.c | 2 +-
5 files changed, 8 insertions(+), 61 deletions(-)
--
2.39.2
next reply other threads:[~2024-08-12 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 10:30 Jani Nikula [this message]
2024-08-12 10:30 ` [PATCH 1/3] drm/xe/tests: remove unused leftover xe_call_for_each_device() Jani Nikula
2024-08-12 10:30 ` [PATCH 2/3] drm/xe: use pdev_to_xe_device() instead of pci_get_drvdata() directly Jani Nikula
2024-08-12 10:30 ` [PATCH 3/3] drm/xe: add kdev_to_xe_device() helper and use it Jani Nikula
2024-08-12 10:36 ` ✓ CI.Patch_applied: success for drm/xe: drvdata cleanups Patchwork
2024-08-12 10:36 ` ✓ CI.checkpatch: " Patchwork
2024-08-12 10:38 ` ✓ CI.KUnit: " Patchwork
2024-08-12 10:54 ` ✓ CI.Build: " Patchwork
2024-08-12 10:57 ` ✓ CI.Hooks: " Patchwork
2024-08-12 10:58 ` ✓ CI.checksparse: " Patchwork
2024-08-12 11:31 ` ✓ CI.BAT: " Patchwork
2024-08-12 14:27 ` ✗ CI.FULL: failure " Patchwork
2024-08-13 9:12 ` [PATCH 0/3] " Jani Nikula
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=cover.1723458544.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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