From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, lucas.demarchi@intel.com,
Gustavo Sousa <gustavo.sousa@intel.com>
Subject: Re: [PATCH v2 0/6] drm/xe & drm/i915: drvdata usage changes follow-up
Date: Mon, 02 Sep 2024 15:20:52 +0300 [thread overview]
Message-ID: <871q22utzv.fsf@intel.com> (raw)
In-Reply-To: <cover.1724942754.git.jani.nikula@intel.com>
On Thu, 29 Aug 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> Follow-up to [1].
Thanks for the reviews, pushed to drm-intel-next.
BR,
Jani.
>
> BR,
> Jani.
>
>
> [1] https://lore.kernel.org/r/cover.1723129920.git.jani.nikula@intel.com
>
> Jani Nikula (6):
> drm/i915 & drm/xe: save struct drm_device to drvdata
> drm/i915: support struct device and pci_dev in to_intel_display()
> drm/i915/audio: migrate away from kdev_to_i915()
> drm/i915/hdcp: migrate away from kdev_to_i915() in bind/unbind
> drm/i915/hdcp: migrate away from kdev_to_i915() in GSC messaging
> drm/xe/display: remove unused compat kdev_to_i915() and pdev_to_i915()
>
> drivers/gpu/drm/i915/display/intel_audio.c | 34 ++++++----
> .../drm/i915/display/intel_display_types.h | 8 ++-
> drivers/gpu/drm/i915/display/intel_hdcp.c | 10 +--
> .../drm/i915/display/intel_hdcp_gsc_message.c | 67 +++++++++++++------
> drivers/gpu/drm/i915/i915_driver.c | 2 +-
> drivers/gpu/drm/i915/i915_drv.h | 8 ++-
> .../gpu/drm/i915/selftests/mock_gem_device.c | 2 +-
> .../gpu/drm/xe/compat-i915-headers/i915_drv.h | 7 --
> drivers/gpu/drm/xe/xe_device.h | 8 ++-
> drivers/gpu/drm/xe/xe_pci.c | 2 +-
> 10 files changed, 94 insertions(+), 54 deletions(-)
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-09-02 12:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 14:47 [PATCH v2 0/6] drm/xe & drm/i915: drvdata usage changes follow-up Jani Nikula
2024-08-29 14:47 ` [PATCH v2 1/6] drm/i915 & drm/xe: save struct drm_device to drvdata Jani Nikula
2024-08-29 14:47 ` [PATCH v2 2/6] drm/i915: support struct device and pci_dev in to_intel_display() Jani Nikula
2024-08-29 14:47 ` [PATCH v2 3/6] drm/i915/audio: migrate away from kdev_to_i915() Jani Nikula
2024-08-29 14:47 ` [PATCH v2 4/6] drm/i915/hdcp: migrate away from kdev_to_i915() in bind/unbind Jani Nikula
2024-08-29 14:47 ` [PATCH v2 5/6] drm/i915/hdcp: migrate away from kdev_to_i915() in GSC messaging Jani Nikula
2024-09-02 8:47 ` Nautiyal, Ankit K
2024-09-02 8:47 ` Kandpal, Suraj
2024-09-02 8:52 ` Murthy, Arun R
2024-09-02 10:44 ` Kandpal, Suraj
2024-08-29 14:47 ` [PATCH v2 6/6] drm/xe/display: remove unused compat kdev_to_i915() and pdev_to_i915() Jani Nikula
2024-08-29 14:54 ` ✓ CI.Patch_applied: success for drm/xe & drm/i915: drvdata usage changes follow-up Patchwork
2024-08-29 14:55 ` ✓ CI.checkpatch: " Patchwork
2024-08-29 14:56 ` ✓ CI.KUnit: " Patchwork
2024-08-29 15:08 ` ✓ CI.Build: " Patchwork
2024-08-29 15:10 ` ✓ CI.Hooks: " Patchwork
2024-08-29 15:12 ` ✗ CI.checksparse: warning " Patchwork
2024-08-29 15:31 ` ✓ CI.BAT: success " Patchwork
2024-08-29 15:42 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-08-29 15:50 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-30 4:50 ` ✗ CI.FULL: failure " Patchwork
2024-08-31 0:09 ` ✗ Fi.CI.IGT: " Patchwork
2024-09-02 12:20 ` Jani Nikula [this message]
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=871q22utzv.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--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.