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: Mon, 12 Aug 2024 13:36:01 +0300 [thread overview]
Message-ID: <8734na2fla.fsf@intel.com> (raw)
In-Reply-To: <luk4l4jlidukwvo5y3cxajcvou2s4gxseopifb6fmltbwysode@lfjilqcrjvgj>
On Fri, 09 Aug 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Aug 09, 2024 at 10:58:24AM GMT, Lucas De Marchi wrote:
>>On Fri, Aug 09, 2024 at 04:23:47PM GMT, Jani Nikula wrote:
>>>On Fri, 09 Aug 2024, Jani Nikula <jani.nikula@intel.com> wrote:
>>>>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.
>>>
>>>In the mean time, ack for merging this via drm-intel-next?
>>
>>
>>Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> oh. wait... but I don't think you will be able to merge the first patch
> through drm-intel-next.
>
> $ git branch --contains 57ecead343e7
> + drm-tip
> + drm-xe-next
> * tip
> + topic/xe-for-CI
>
> Sorry for not noticing that before. Alternatives:
>
> 1)
> merge this patch via drm-xe-next, and possibly (if it unblocks more
> patches on top), your 'drm/xe/tests: fix drvdata usage" from v1' via
> drm-intel.
>
> 2) do not apply this and patch 10 until we are back in sync.
>
> ... something else?
Yeah, something else. I resent patches 1-3 separately to be merged via
drm-xe-next [1] and patch 4 to be merged via drm-intel-next [2]. Clean
and straightforward.
Let's do the rest once we're back in sync.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1723458544.git.jani.nikula@intel.com
[2] https://lore.kernel.org/r/20240812103415.1540096-1-jani.nikula@intel.com
>
> I don't have a preference.
>
> Lucas De Marchi
>
>>
>>thanks
>>Lucas De Marchi
>>
>>>
>>>BR,
>>>Jani.
>>>
>>>>
>>>>BR,
>>>>Jani.
>>>
>>>--
>>>Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-12 10:36 UTC|newest]
Thread overview: 33+ 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:21 ` ✓ CI.Patch_applied: success for drm/xe & drm/i915: drvdata usage changes (rev2) Patchwork
2024-08-08 15:21 ` ✓ CI.checkpatch: " Patchwork
2024-08-08 15:23 ` ✓ CI.KUnit: " Patchwork
2024-08-08 15:34 ` ✓ CI.Build: " Patchwork
2024-08-08 15:37 ` ✓ CI.Hooks: " Patchwork
2024-08-08 15:38 ` ✗ CI.checksparse: warning " Patchwork
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
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 [this message]
2024-08-08 15:53 ` ✗ Fi.CI.SPARSE: warning for drm/xe & drm/i915: drvdata usage changes (rev2) Patchwork
2024-08-08 15:58 ` ✓ CI.BAT: success " Patchwork
2024-08-08 15:59 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-08 17:01 ` ✗ CI.FULL: failure " Patchwork
2024-08-08 19:02 ` ✗ 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=8734na2fla.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.