From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
Gustavo Sousa <gustavo.sousa@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 00/10] drm/xe & drm/i915: drvdata usage changes
Date: Fri, 09 Aug 2024 12:06:55 +0300 [thread overview]
Message-ID: <87mslm2hg0.fsf@intel.com> (raw)
In-Reply-To: <2pep6oj5dd7ocei2a3egnm3agoa46nxad2e6e2riwby66khfpt@22g2ari2u4ps>
On Thu, 08 Aug 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Thu, Aug 08, 2024 at 06:15:45PM GMT, Jani Nikula wrote:
>>v2 of https://patchwork.freedesktop.org/series/136621/
>>
>>Removed "drm/xe/tests: fix drvdata usage" from v1 in favour of
>>"drm/xe/tests: remove unused leftover xe_call_for_each_device()" here.
>>
>>Due to the display dependency, I think it would be best to merge the
>>whole thing via drm-intel-next, and do the first drm-intel-next pull
>>request and backmerge from drm-next to drm-xe-next in fairly quick
>>succession.
>
> I was waiting the drm-intel-next pull to do a backmerge as we started to
> have some big divergences. I will try to review the missing patches to
> expedite that. Are you planning a pull this week?
Rodrigo? I think it's your shift.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-09 9:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 15:15 [PATCH v2 00/10] drm/xe & drm/i915: drvdata usage changes Jani Nikula
2024-08-08 15:15 ` [PATCH v2 01/10] drm/xe/tests: remove unused leftover xe_call_for_each_device() Jani Nikula
2024-08-09 12:53 ` Gustavo Sousa
2024-08-08 15:15 ` [PATCH v2 02/10] drm/xe: use pdev_to_xe_device() instead of pci_get_drvdata() directly Jani Nikula
2024-08-08 15:15 ` [PATCH v2 03/10] drm/xe: add kdev_to_xe_device() helper and use it Jani Nikula
2024-08-08 15:15 ` [PATCH v2 04/10] drm/i915: use pdev_to_i915() instead of pci_get_drvdata() directly Jani Nikula
2024-08-09 12:54 ` Gustavo Sousa
2024-08-12 17:15 ` Andi Shyti
2024-08-08 15:15 ` [PATCH v2 05/10] drm/i915 & drm/xe: save struct drm_device to drvdata Jani Nikula
2024-08-08 15:15 ` [PATCH v2 06/10] drm/i915: support struct device and pci_dev in to_intel_display() Jani Nikula
2024-08-09 12:55 ` Gustavo Sousa
2024-08-08 15:15 ` [PATCH v2 07/10] drm/i915/audio: migrate away from kdev_to_i915() Jani Nikula
2024-08-08 15:15 ` [PATCH v2 08/10] drm/i915/hdcp: migrate away from kdev_to_i915() in bind/unbind Jani Nikula
2024-08-08 15:15 ` [PATCH v2 09/10] drm/i915/hdcp: migrate away from kdev_to_i915() in GSC messaging Jani Nikula
2024-08-09 13:05 ` Gustavo Sousa
2024-08-08 15:15 ` [PATCH v2 10/10] drm/xe/display: remove unused compat kdev_to_i915() and pdev_to_i915() Jani Nikula
2024-08-08 15:48 ` [PATCH v2 00/10] drm/xe & drm/i915: drvdata usage changes Lucas De Marchi
2024-08-09 9:06 ` Jani Nikula [this message]
2024-08-09 13:23 ` Jani Nikula
2024-08-09 15:58 ` Lucas De Marchi
2024-08-09 16:25 ` Lucas De Marchi
2024-08-12 10:36 ` Jani Nikula
2024-08-08 15:53 ` ✗ Fi.CI.SPARSE: warning for drm/xe & drm/i915: drvdata usage changes (rev2) Patchwork
2024-08-08 15:59 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-08 19:02 ` ✗ Fi.CI.IGT: failure " 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=87mslm2hg0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox