From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@kernel.org>
Cc: intel-xe@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-xe] [PATCH] fixup! drm/i915/display: Remaining changes to make xe compile
Date: Wed, 17 May 2023 10:53:20 +0300 [thread overview]
Message-ID: <87sfbvgzrj.fsf@intel.com> (raw)
In-Reply-To: <ZGPuwpv4tg03730V@rdvivi-mobl4>
On Tue, 16 May 2023, Rodrigo Vivi <rodrigo.vivi@kernel.org> wrote:
> On Thu, May 11, 2023 at 12:28:28PM +0300, Jani Nikula wrote:
>> The dsparb_lock may be coming back with [1] later, but adding it here is
>> probably just a rebase leftover. Drop it.
>>
>> [1] https://patchwork.freedesktop.org/patch/msgid/20230327161223.406573-1-rodrigo.vivi@intel.com
>
> ouch...
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Thanks, pushed.
>
>
>>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_display_core.h | 3 ---
>> drivers/gpu/drm/i915/i915_driver.c | 1 -
>> 2 files changed, 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
>> index 437f623337e3..e36f88a39b86 100644
>> --- a/drivers/gpu/drm/i915/display/intel_display_core.h
>> +++ b/drivers/gpu/drm/i915/display/intel_display_core.h
>> @@ -264,9 +264,6 @@ struct intel_wm {
>> */
>> struct mutex wm_mutex;
>>
>> - /* protects DSPARB registers on pre-g4x/vlv/chv */
>> - spinlock_t dsparb_lock;
>> -
>> bool ipc_enabled;
>> };
>>
>> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
>> index 5d302602793c..12ba7cf78b1e 100644
>> --- a/drivers/gpu/drm/i915/i915_driver.c
>> +++ b/drivers/gpu/drm/i915/i915_driver.c
>> @@ -215,7 +215,6 @@ static int i915_driver_early_probe(struct drm_i915_private *dev_priv)
>> spin_lock_init(&dev_priv->irq_lock);
>> spin_lock_init(&dev_priv->gpu_error.lock);
>> spin_lock_init(&dev_priv->display.fb_tracking.lock);
>> - spin_lock_init(&dev_priv->display.wm.dsparb_lock);
>> mutex_init(&dev_priv->display.backlight.lock);
>>
>> mutex_init(&dev_priv->sb_lock);
>> --
>> 2.39.2
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-05-17 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 9:28 [Intel-xe] [PATCH] fixup! drm/i915/display: Remaining changes to make xe compile Jani Nikula
2023-05-11 9:31 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-05-11 9:32 ` [Intel-xe] ✗ CI.KUnit: failure " Patchwork
2023-05-16 20:59 ` [Intel-xe] [PATCH] " Rodrigo Vivi
2023-05-17 7:53 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-11 12:29 Jani Nikula
2023-05-11 22:24 ` Lucas De Marchi
2023-05-12 7:28 ` Jani Nikula
2023-08-03 10:53 Jani Nikula
2023-08-07 22:09 ` Rodrigo Vivi
2023-08-08 7:46 ` 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=87sfbvgzrj.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=rodrigo.vivi@kernel.org \
/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