From: Jani Nikula <jani.nikula@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>,
intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [Intel-xe] [PATCH v3 1/6] drm/i915: Initialize dkl_phy spin lock from display code path
Date: Tue, 11 Apr 2023 11:33:32 +0300 [thread overview]
Message-ID: <87bkjues2r.fsf@intel.com> (raw)
In-Reply-To: <87edoqes4r.fsf@intel.com>
On Tue, 11 Apr 2023, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 10 Apr 2023, José Roberto de Souza <jose.souza@intel.com> wrote:
>> Start to move the initialization of some lock from
>> i915_driver_early_probe().
>
> Please send this as standalone patch to i915. It won't get merged to
> i915 as part of series only parts of which apply to i915.
Not to mention drm-xe-next is *not* the path to upstream i915
changes. Each i915 merged there is a potential problem in upstreaming
xe.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>,
intel-xe@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH v3 1/6] drm/i915: Initialize dkl_phy spin lock from display code path
Date: Tue, 11 Apr 2023 11:33:32 +0300 [thread overview]
Message-ID: <87bkjues2r.fsf@intel.com> (raw)
In-Reply-To: <87edoqes4r.fsf@intel.com>
On Tue, 11 Apr 2023, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 10 Apr 2023, José Roberto de Souza <jose.souza@intel.com> wrote:
>> Start to move the initialization of some lock from
>> i915_driver_early_probe().
>
> Please send this as standalone patch to i915. It won't get merged to
> i915 as part of series only parts of which apply to i915.
Not to mention drm-xe-next is *not* the path to upstream i915
changes. Each i915 merged there is a potential problem in upstreaming
xe.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-04-11 8:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 18:32 [Intel-gfx] [PATCH v3 1/6] drm/i915: Initialize dkl_phy spin lock from display code path José Roberto de Souza
2023-04-10 18:32 ` [Intel-xe] " José Roberto de Souza
2023-04-10 18:32 ` [Intel-gfx] [PATCH v3 2/6] drm/i915: Only initialize dlk phy lock in display 12 and newer José Roberto de Souza
2023-04-10 18:32 ` [Intel-xe] " José Roberto de Souza
2023-04-11 8:38 ` [Intel-gfx] " Ville Syrjälä
2023-04-11 8:38 ` [Intel-xe] " Ville Syrjälä
2023-04-10 18:32 ` [Intel-xe] [PATCH v3 3/6] fixup! drm/i915/display: Remaining changes to make xe compile José Roberto de Souza
2023-04-10 18:32 ` [Intel-xe] [PATCH v3 4/6] TEMPORARY: drm/xe/display: Enable modular fia in TGL José Roberto de Souza
2023-04-10 18:32 ` [Intel-xe] [PATCH v3 5/6] drm/xe/display: Disable PSR HW tracking by default in all display versions José Roberto de Souza
2023-04-10 18:32 ` [Intel-xe] [PATCH v3 6/6] drm/xe: Enable Raptorlake-P José Roberto de Souza
2023-04-10 19:02 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v3,1/6] drm/i915: Initialize dkl_phy spin lock from display code path Patchwork
2023-04-10 19:03 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-04-10 19:07 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-04-10 19:29 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-04-11 8:32 ` [Intel-gfx] [Intel-xe] [PATCH v3 1/6] " Jani Nikula
2023-04-11 8:32 ` Jani Nikula
2023-04-11 8:33 ` Jani Nikula [this message]
2023-04-11 8:33 ` Jani Nikula
2023-04-11 13:24 ` [Intel-gfx] " Souza, Jose
2023-04-11 13:24 ` Souza, Jose
2023-04-11 8:39 ` [Intel-gfx] " Ville Syrjälä
2023-04-11 8:39 ` [Intel-xe] " Ville Syrjälä
2023-04-11 8:51 ` [Intel-gfx] [Intel-xe] " Jani Nikula
2023-04-11 8:51 ` [Intel-xe] [Intel-gfx] " Jani Nikula
2023-04-11 9:12 ` [Intel-gfx] [Intel-xe] " Ville Syrjälä
2023-04-11 9:12 ` [Intel-xe] [Intel-gfx] " Ville Syrjälä
2023-04-11 9:14 ` [Intel-gfx] [Intel-xe] " Jani Nikula
2023-04-11 9:14 ` [Intel-xe] [Intel-gfx] " Jani Nikula
2023-04-11 14:51 ` [Intel-gfx] [Intel-xe] " Rodrigo Vivi
2023-04-11 14:51 ` [Intel-xe] [Intel-gfx] " Rodrigo Vivi
2023-04-11 19:59 ` [Intel-gfx] [Intel-xe] " Lucas De Marchi
2023-04-11 19:59 ` [Intel-xe] [Intel-gfx] " Lucas De Marchi
2023-04-11 20:07 ` [Intel-gfx] [Intel-xe] " Souza, Jose
2023-04-11 20:07 ` [Intel-xe] [Intel-gfx] " Souza, Jose
2023-04-11 21:20 ` [Intel-gfx] [Intel-xe] " Lucas De Marchi
2023-04-11 21:20 ` [Intel-xe] [Intel-gfx] " Lucas De Marchi
2023-04-12 17:13 ` [Intel-gfx] [Intel-xe] " Souza, Jose
2023-04-12 17:13 ` [Intel-xe] [Intel-gfx] " Souza, Jose
2023-04-13 8:22 ` [Intel-gfx] [Intel-xe] " Jani Nikula
2023-04-13 8:22 ` [Intel-xe] [Intel-gfx] " Jani Nikula
2023-04-13 9:49 ` [Intel-gfx] [Intel-xe] " Jani Nikula
2023-04-13 9:49 ` [Intel-xe] [Intel-gfx] " 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=87bkjues2r.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@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.