Subject: linux-next: manual merge of the drm-intel tree with Linus' tree

From: Stephen Rothwell <[email-masked]>
Date: Tue, 18 Oct 2022 09:05:41 +1100

Hi all,

Today's linux-next merge of the drm-intel tree got a conflict in:

  drivers/gpu/drm/i915/i915_driver.c

between commit:

  1c66a12ab431 ("drm/i915: Handle each GT on init/release and suspend/resume")

from Linus' tree and commit:

  3703060d17b0 ("drm/i915/display: remove drm_device aliases")

from the drm-intel tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/gpu/drm/i915/i915_driver.c
index c459eb362c47,e7b2ebc6b88d..000000000000
--- a/drivers/gpu/drm/i915/i915_driver.c
+++ b/drivers/gpu/drm/i915/i915_driver.c
@@@ -337,10 -324,11 +337,11 @@@ static int i915_driver_early_probe(stru
  	if (i915_inject_probe_failure(dev_priv))
  		return -ENODEV;
  
- 	intel_device_info_subplatform_init(dev_priv);
+ 	intel_device_info_runtime_init_early(dev_priv);
+ 
  	intel_step_init(dev_priv);
  
 -	intel_uncore_mmio_debug_init_early(&dev_priv->mmio_debug);
 +	intel_uncore_mmio_debug_init_early(dev_priv);
  
  	spin_lock_init(&dev_priv->irq_lock);
  	spin_lock_init(&dev_priv->gpu_error.lock);
@@@ -738,10 -716,6 +739,9 @@@ static void i915_driver_hw_remove(struc
   */
  static void i915_driver_register(struct drm_i915_private *dev_priv)
  {
- 	struct drm_device *dev = &dev_priv->drm;
 +	struct intel_gt *gt;
 +	unsigned int i;
 +
  	i915_gem_driver_register(dev_priv);
  	i915_pmu_register(dev_priv);