All of lore.kernel.org
 help / color / mirror / Atom feed
From: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Mihail Atanassov <Mihail.Atanassov@arm.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	nd@arm.com
Subject: Re: [PATCH 36/44] drm/komeda: use devm_drm_dev_alloc
Date: Wed, 8 Apr 2020 16:40:40 +0800	[thread overview]
Message-ID: <20200408084040.GA11347@jamwan02-TSP300> (raw)
In-Reply-To: <20200403135828.2542770-37-daniel.vetter@ffwll.ch>

On Fri, Apr 03, 2020 at 09:58:20PM +0800, Daniel Vetter wrote:
> Komeda uses the component framework, which does open/close a new
> devres group around all the bind callbacks. Which means we can use
> devm_ functions for managing the drm_device cleanup, with leaking
> stuff in case of deferred probes or other reasons to unbind
> components, or the component_master.
> 
> Also note that this fixes a double-free in the probe unroll code, bot
> drm_dev_put and kfree(kms) result in the kms allocation getting freed.
> 
> Aside: komeda_bind could be cleaned up a lot, devm_kfree is a bit
> redundant. Plus I'm not clear on why there's suballocations for
> mdrv->mdev and mdrv->kms. Plus I'm not sure the lifetimes are correct
> with all that devm_kzalloc usage ... That structure layout is also the
> reason why komeda still uses drm_device->dev_private and can't easily
> be replaced with a proper container_of upcasting. I'm pretty sure that
> there's endless amounts of hotunplug/hotremove bugs in there with all
> the unprotected dereferencing of drm_device->dev_private.

Hi Daniel:

Thank you for the patch.

Reviewed-by: James Qian Wang <james.qian.wang@arm.com>

For why komeda has two devices komeda_dev and komeda_kms_dev. 
That because komeda treats drm_crtc/plane as virtual, which pick the real
komeda resources to satify the user's requirement. In the initial driver
design we want to clear the difference of these two class structures
so we defined two devices:

- komeda_dev:
  managing the real komeda device and resources.

- komeda_kms_dev
  the virtual device managing the drm related stuff like
  komeda_crtc/plane.

And yes, even for that we don't need two sub-allocations, we are planing
to move the komeda_dev into the komeda_kms_dev or just merge two devices
together.

Thanks
James

> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> Cc: "James (Qian) Wang" <james.qian.wang@arm.com>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
> Cc: Mihail Atanassov <mihail.atanassov@arm.com>
> ---
>  drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 16 +++++-----------
>  1 file changed, 5 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_kms.c b/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
> index 16dfd5cdb66c..6b85d5f4caa8 100644
> --- a/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
> +++ b/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
> @@ -261,18 +261,16 @@ static void komeda_kms_mode_config_init(struct komeda_kms_dev *kms,
>  
>  struct komeda_kms_dev *komeda_kms_attach(struct komeda_dev *mdev)
>  {
> -	struct komeda_kms_dev *kms = kzalloc(sizeof(*kms), GFP_KERNEL);
> +	struct komeda_kms_dev *kms;
>  	struct drm_device *drm;
>  	int err;
>  
> -	if (!kms)
> -		return ERR_PTR(-ENOMEM);
> +	kms = devm_drm_dev_alloc(mdev->dev, &komeda_kms_driver,
> +				 struct komeda_kms_dev, base);
> +	if (IS_ERR(kms))
> +		return kms;
>  
>  	drm = &kms->base;
> -	err = drm_dev_init(drm, &komeda_kms_driver, mdev->dev);
> -	if (err)
> -		goto free_kms;
> -	drmm_add_final_kfree(drm, kms);
>  
>  	drm->dev_private = mdev;
>  
> @@ -329,9 +327,6 @@ struct komeda_kms_dev *komeda_kms_attach(struct komeda_dev *mdev)
>  	drm_mode_config_cleanup(drm);
>  	komeda_kms_cleanup_private_objs(kms);
>  	drm->dev_private = NULL;
> -	drm_dev_put(drm);
> -free_kms:
> -	kfree(kms);
>  	return ERR_PTR(err);
>  }
>  
> @@ -348,5 +343,4 @@ void komeda_kms_detach(struct komeda_kms_dev *kms)
>  	drm_mode_config_cleanup(drm);
>  	komeda_kms_cleanup_private_objs(kms);
>  	drm->dev_private = NULL;
> -	drm_dev_put(drm);
>  }
> -- 
> 2.25.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Mihail Atanassov <Mihail.Atanassov@arm.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	nd@arm.com
Subject: Re: [Intel-gfx] [PATCH 36/44] drm/komeda: use devm_drm_dev_alloc
Date: Wed, 8 Apr 2020 16:40:40 +0800	[thread overview]
Message-ID: <20200408084040.GA11347@jamwan02-TSP300> (raw)
In-Reply-To: <20200403135828.2542770-37-daniel.vetter@ffwll.ch>

On Fri, Apr 03, 2020 at 09:58:20PM +0800, Daniel Vetter wrote:
> Komeda uses the component framework, which does open/close a new
> devres group around all the bind callbacks. Which means we can use
> devm_ functions for managing the drm_device cleanup, with leaking
> stuff in case of deferred probes or other reasons to unbind
> components, or the component_master.
> 
> Also note that this fixes a double-free in the probe unroll code, bot
> drm_dev_put and kfree(kms) result in the kms allocation getting freed.
> 
> Aside: komeda_bind could be cleaned up a lot, devm_kfree is a bit
> redundant. Plus I'm not clear on why there's suballocations for
> mdrv->mdev and mdrv->kms. Plus I'm not sure the lifetimes are correct
> with all that devm_kzalloc usage ... That structure layout is also the
> reason why komeda still uses drm_device->dev_private and can't easily
> be replaced with a proper container_of upcasting. I'm pretty sure that
> there's endless amounts of hotunplug/hotremove bugs in there with all
> the unprotected dereferencing of drm_device->dev_private.

Hi Daniel:

Thank you for the patch.

Reviewed-by: James Qian Wang <james.qian.wang@arm.com>

For why komeda has two devices komeda_dev and komeda_kms_dev. 
That because komeda treats drm_crtc/plane as virtual, which pick the real
komeda resources to satify the user's requirement. In the initial driver
design we want to clear the difference of these two class structures
so we defined two devices:

- komeda_dev:
  managing the real komeda device and resources.

- komeda_kms_dev
  the virtual device managing the drm related stuff like
  komeda_crtc/plane.

And yes, even for that we don't need two sub-allocations, we are planing
to move the komeda_dev into the komeda_kms_dev or just merge two devices
together.

Thanks
James

> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> Cc: "James (Qian) Wang" <james.qian.wang@arm.com>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
> Cc: Mihail Atanassov <mihail.atanassov@arm.com>
> ---
>  drivers/gpu/drm/arm/display/komeda/komeda_kms.c | 16 +++++-----------
>  1 file changed, 5 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_kms.c b/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
> index 16dfd5cdb66c..6b85d5f4caa8 100644
> --- a/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
> +++ b/drivers/gpu/drm/arm/display/komeda/komeda_kms.c
> @@ -261,18 +261,16 @@ static void komeda_kms_mode_config_init(struct komeda_kms_dev *kms,
>  
>  struct komeda_kms_dev *komeda_kms_attach(struct komeda_dev *mdev)
>  {
> -	struct komeda_kms_dev *kms = kzalloc(sizeof(*kms), GFP_KERNEL);
> +	struct komeda_kms_dev *kms;
>  	struct drm_device *drm;
>  	int err;
>  
> -	if (!kms)
> -		return ERR_PTR(-ENOMEM);
> +	kms = devm_drm_dev_alloc(mdev->dev, &komeda_kms_driver,
> +				 struct komeda_kms_dev, base);
> +	if (IS_ERR(kms))
> +		return kms;
>  
>  	drm = &kms->base;
> -	err = drm_dev_init(drm, &komeda_kms_driver, mdev->dev);
> -	if (err)
> -		goto free_kms;
> -	drmm_add_final_kfree(drm, kms);
>  
>  	drm->dev_private = mdev;
>  
> @@ -329,9 +327,6 @@ struct komeda_kms_dev *komeda_kms_attach(struct komeda_dev *mdev)
>  	drm_mode_config_cleanup(drm);
>  	komeda_kms_cleanup_private_objs(kms);
>  	drm->dev_private = NULL;
> -	drm_dev_put(drm);
> -free_kms:
> -	kfree(kms);
>  	return ERR_PTR(err);
>  }
>  
> @@ -348,5 +343,4 @@ void komeda_kms_detach(struct komeda_kms_dev *kms)
>  	drm_mode_config_cleanup(drm);
>  	komeda_kms_cleanup_private_objs(kms);
>  	drm->dev_private = NULL;
> -	drm_dev_put(drm);
>  }
> -- 
> 2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-04-08  8:41 UTC|newest]

Thread overview: 262+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 13:57 [PATCH 00/44] devm_drm_dev_alloc, no more drmm_add_final_kfree Daniel Vetter
2020-04-03 13:57 ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 01/44] drivers/base: Always release devres on device_del Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 14:17   ` Greg Kroah-Hartman
2020-04-03 14:17     ` [Intel-gfx] " Greg Kroah-Hartman
2020-04-03 14:47     ` Daniel Vetter
2020-04-03 14:47       ` [Intel-gfx] " Daniel Vetter
2020-04-03 14:51       ` Daniel Vetter
2020-04-03 14:51         ` [Intel-gfx] " Daniel Vetter
2020-04-03 15:01         ` Greg Kroah-Hartman
2020-04-03 15:01           ` [Intel-gfx] " Greg Kroah-Hartman
2020-04-03 15:06       ` Greg Kroah-Hartman
2020-04-03 15:06         ` [Intel-gfx] " Greg Kroah-Hartman
2020-04-03 15:15         ` Daniel Vetter
2020-04-03 15:15           ` [Intel-gfx] " Daniel Vetter
2020-04-03 15:33           ` Daniel Vetter
2020-04-03 15:33             ` [Intel-gfx] " Daniel Vetter
2020-04-06 12:32   ` Daniel Vetter
2020-04-06 12:32     ` [Intel-gfx] " Daniel Vetter
2020-04-06 13:38     ` Greg Kroah-Hartman
2020-04-06 13:38       ` [Intel-gfx] " Greg Kroah-Hartman
2020-04-06 13:55       ` Daniel Vetter
2020-04-06 13:55         ` [Intel-gfx] " Daniel Vetter
2020-04-28 13:15         ` Daniel Vetter
2020-04-28 13:15           ` [Intel-gfx] " Daniel Vetter
2020-05-15 12:55           ` Greg Kroah-Hartman
2020-05-15 12:55             ` [Intel-gfx] " Greg Kroah-Hartman
2020-05-15 14:05             ` Daniel Vetter
2020-05-15 14:05               ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 02/44] drm: Add devm_drm_dev_alloc macro Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-05 10:20   ` Noralf Trønnes
2020-04-05 10:20     ` [Intel-gfx] " Noralf Trønnes
2020-04-06 12:00   ` Laurent Pinchart
2020-04-06 12:00     ` [Intel-gfx] " Laurent Pinchart
2020-04-06 12:18     ` Daniel Vetter
2020-04-06 12:18       ` [Intel-gfx] " Daniel Vetter
2020-04-08  6:57   ` Sam Ravnborg
2020-04-08  6:57     ` [Intel-gfx] " Sam Ravnborg
2020-04-08 12:11     ` Daniel Vetter
2020-04-08 12:11       ` [Intel-gfx] " Daniel Vetter
2020-04-08 18:55       ` Sam Ravnborg
2020-04-08 18:55         ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:57 ` [PATCH 03/44] drm/device: Deprecate dev_private harder Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:02   ` Sam Ravnborg
2020-04-08  7:02     ` [Intel-gfx] " Sam Ravnborg
2020-04-14 16:43     ` Daniel Vetter
2020-04-14 16:43       ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 04/44] drm/vgem: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 05/44] drm/vkms: " Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 06/44] drm/vboxvideo: drop DRM_MTRR_WC #define Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:03   ` Sam Ravnborg
2020-04-08  7:03     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:57 ` [PATCH 07/44] drm/vboxvideo: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 08/44] drm/vboxvideo: Stop using drm_device->dev_private Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-06 11:56   ` Thomas Zimmermann
2020-04-06 11:56     ` [Intel-gfx] " Thomas Zimmermann
2020-04-07  7:24     ` Daniel Vetter
2020-04-07  7:24       ` [Intel-gfx] " Daniel Vetter
2020-04-08  6:33       ` Thomas Zimmermann
2020-04-08  6:33         ` [Intel-gfx] " Thomas Zimmermann
2020-04-08  7:19   ` Sam Ravnborg
2020-04-08  7:19     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:57 ` [PATCH 09/44] drm/vboxvidoe: use managed pci functions Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:21   ` Sam Ravnborg
2020-04-08  7:21     ` [Intel-gfx] " Sam Ravnborg
2020-04-14 16:30     ` Daniel Vetter
2020-04-14 16:30       ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 10/44] drm/vboxvideo: Use devm_gen_pool_create Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:24   ` Sam Ravnborg
2020-04-08  7:24     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:57 ` [PATCH 11/44] drm/v3d: Don't set drm_device->dev_private Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:39   ` Eric Anholt
2020-04-03 17:39     ` [Intel-gfx] " Eric Anholt
2020-04-03 13:57 ` [PATCH 12/44] drm/v3d: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:38   ` Eric Anholt
2020-04-03 17:38     ` [Intel-gfx] " Eric Anholt
2020-04-03 13:57 ` [PATCH 13/44] drm/v3d: Delete v3d_dev->dev Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:35   ` Eric Anholt
2020-04-03 17:35     ` [Intel-gfx] " Eric Anholt
2020-04-03 13:57 ` [PATCH 14/44] drm/v3d: Delete v3d_dev->pdev Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:35   ` Eric Anholt
2020-04-03 17:35     ` [Intel-gfx] " Eric Anholt
2020-04-08  7:27   ` Sam Ravnborg
2020-04-08  7:27     ` [Intel-gfx] " Sam Ravnborg
2020-04-08 12:13     ` Daniel Vetter
2020-04-08 12:13       ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:57 ` [PATCH 15/44] drm/udl: Use demv_drm_dev_alloc Daniel Vetter
2020-04-03 13:57   ` [Intel-gfx] " Daniel Vetter
2020-04-05 10:18   ` Noralf Trønnes
2020-04-05 10:18     ` [Intel-gfx] " Noralf Trønnes
2020-04-05 13:47     ` Daniel Vetter
2020-04-05 13:47       ` [Intel-gfx] " Daniel Vetter
2020-04-05 14:46       ` Noralf Trønnes
2020-04-05 14:46         ` [Intel-gfx] " Noralf Trønnes
2020-04-06 12:05     ` Thomas Zimmermann
2020-04-06 12:05       ` [Intel-gfx] " Thomas Zimmermann
2020-04-03 13:58 ` [PATCH 16/44] drm/udl: don't set drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-06 11:52   ` Thomas Zimmermann
2020-04-06 11:52     ` [Intel-gfx] " Thomas Zimmermann
2020-04-08  7:29   ` Sam Ravnborg
2020-04-08  7:29     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:58 ` [PATCH 17/44] drm/st7735r: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:00   ` David Lechner
2020-04-03 17:00     ` [Intel-gfx] " David Lechner
2020-04-03 13:58 ` [PATCH 18/44] drm/st7586: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:01   ` David Lechner
2020-04-03 17:01     ` [Intel-gfx] " David Lechner
2020-04-03 13:58 ` [PATCH 19/44] drm/repaper: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-05 10:00   ` Noralf Trønnes
2020-04-05 10:00     ` [Intel-gfx] " Noralf Trønnes
2020-04-03 13:58 ` [PATCH 20/44] drm/mi0283qt: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-05 10:01   ` Noralf Trønnes
2020-04-05 10:01     ` [Intel-gfx] " Noralf Trønnes
2020-04-03 13:58 ` [PATCH 21/44] drm/ili9486: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-05 10:02   ` Noralf Trønnes
2020-04-05 10:02     ` [Intel-gfx] " Noralf Trønnes
2020-04-03 13:58 ` [PATCH 22/44] drm/ili9341: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:02   ` David Lechner
2020-04-03 17:02     ` [Intel-gfx] " David Lechner
2020-04-03 13:58 ` [PATCH 23/44] drm/ili9225: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:02   ` David Lechner
2020-04-03 17:02     ` [Intel-gfx] " David Lechner
2020-04-03 13:58 ` [PATCH 24/44] drm/hx8357d: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 17:38   ` Eric Anholt
2020-04-03 17:38     ` [Intel-gfx] " Eric Anholt
2020-04-03 13:58 ` [PATCH 25/44] drm/gm12u320: " Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 26/44] drm/gm12u320: Don't use drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 27/44] drm/tidss: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:52   ` Sam Ravnborg
2020-04-08  7:52     ` [Intel-gfx] " Sam Ravnborg
2020-04-14  9:55   ` Jyri Sarha
2020-04-14  9:55     ` [Intel-gfx] " Jyri Sarha
2020-04-03 13:58 ` [PATCH 28/44] drm/tidss: Don't use drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:52   ` Sam Ravnborg
2020-04-08  7:52     ` [Intel-gfx] " Sam Ravnborg
2020-04-14  9:55   ` Jyri Sarha
2020-04-14  9:55     ` [Intel-gfx] " Jyri Sarha
2020-04-03 13:58 ` [PATCH 29/44] drm/tidss: Delete tidss->saved_state Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:53   ` Sam Ravnborg
2020-04-08  7:53     ` [Intel-gfx] " Sam Ravnborg
2020-04-14  9:55   ` Jyri Sarha
2020-04-14  9:55     ` [Intel-gfx] " Jyri Sarha
2020-04-03 13:58 ` [PATCH 30/44] drm/qxl: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58   ` Daniel Vetter
2020-04-06  6:55   ` Gerd Hoffmann
2020-04-06  6:55     ` [Intel-gfx] " Gerd Hoffmann
2020-04-06  6:55     ` Gerd Hoffmann
2020-04-06 12:11   ` Thomas Zimmermann
2020-04-06 12:11     ` [Intel-gfx] " Thomas Zimmermann
2020-04-06 12:11     ` Thomas Zimmermann
2020-04-07  7:19     ` Daniel Vetter
2020-04-07  7:19       ` [Intel-gfx] " Daniel Vetter
2020-04-07  7:19       ` Daniel Vetter
2020-04-03 13:58 ` [PATCH 31/44] drm/qxl: Don't use drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58   ` Daniel Vetter
2020-04-06  6:55   ` Gerd Hoffmann
2020-04-06  6:55     ` [Intel-gfx] " Gerd Hoffmann
2020-04-06  6:55     ` Gerd Hoffmann
2020-04-03 13:58 ` [PATCH 32/44] drm/mcde: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:57   ` Sam Ravnborg
2020-04-08  7:57     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:58 ` [PATCH 33/44] drm/mcde: Don't use drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:58   ` Sam Ravnborg
2020-04-08  7:58     ` [Intel-gfx] " Sam Ravnborg
2020-04-12  0:44   ` Linus Walleij
2020-04-12  0:44     ` [Intel-gfx] " Linus Walleij
2020-04-03 13:58 ` [PATCH 34/44] drm/ingenic: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  7:59   ` Sam Ravnborg
2020-04-08  7:59     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:58 ` [PATCH 35/44] drm/ingenic: Don't set drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  8:00   ` Sam Ravnborg
2020-04-08  8:00     ` [Intel-gfx] " Sam Ravnborg
2020-04-03 13:58 ` [PATCH 36/44] drm/komeda: use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-08  8:40   ` james qian wang (Arm Technology China) [this message]
2020-04-08  8:40     ` james qian wang (Arm Technology China)
2020-04-08  9:03     ` Daniel Vetter
2020-04-08  9:03       ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 37/44] drm/armada: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 38/44] drm/armada: Don't use drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 39/44] drm/cirrus: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58   ` Daniel Vetter
2020-04-05 10:04   ` Noralf Trønnes
2020-04-05 10:04     ` [Intel-gfx] " Noralf Trønnes
2020-04-05 10:04     ` Noralf Trønnes
2020-04-08  8:01   ` Sam Ravnborg
2020-04-08  8:01     ` [Intel-gfx] " Sam Ravnborg
2020-04-08  8:01     ` Sam Ravnborg
2020-04-03 13:58 ` [PATCH 40/44] drm/cirrus: Don't use drm_device->dev_private Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58   ` Daniel Vetter
2020-04-03 17:40   ` Eric Anholt
2020-04-03 17:40     ` [Intel-gfx] " Eric Anholt
2020-04-03 17:40     ` Eric Anholt
2020-04-06 11:58   ` Thomas Zimmermann
2020-04-06 11:58     ` [Intel-gfx] " Thomas Zimmermann
2020-04-06 11:58     ` Thomas Zimmermann
2020-04-08  8:04     ` Sam Ravnborg
2020-04-08  8:04       ` [Intel-gfx] " Sam Ravnborg
2020-04-08  8:04       ` Sam Ravnborg
2020-04-08  8:01   ` Sam Ravnborg
2020-04-08  8:01     ` [Intel-gfx] " Sam Ravnborg
2020-04-08  8:01     ` Sam Ravnborg
2020-04-03 13:58 ` [PATCH 41/44] drm/i915: Use devm_drm_dev_alloc Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 42/44] drm/i915/selftest: Create mock_destroy_device Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 22:31   ` [PATCH] " Daniel Vetter
2020-04-03 22:31     ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 43/44] drm/i915/selftests: align more to real device lifetimes Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-03 22:31   ` [PATCH] " Daniel Vetter
2020-04-03 22:31     ` [Intel-gfx] " Daniel Vetter
2020-04-03 13:58 ` [PATCH 44/44] drm/managed: Cleanup of unused functions and polishing docs Daniel Vetter
2020-04-03 13:58   ` [Intel-gfx] " Daniel Vetter
2020-04-05 10:29   ` Noralf Trønnes
2020-04-05 10:29     ` [Intel-gfx] " Noralf Trønnes
2020-04-03 14:15 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for devm_drm_dev_alloc, no more drmm_add_final_kfree Patchwork
2020-04-03 23:01 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for devm_drm_dev_alloc, no more drmm_add_final_kfree (rev3) Patchwork
2020-04-03 23:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-04-04 10:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-04-08  8:08 ` [PATCH 00/44] devm_drm_dev_alloc, no more drmm_add_final_kfree Sam Ravnborg
2020-04-08  8:08   ` [Intel-gfx] " Sam Ravnborg
2020-04-08 12:15   ` Daniel Vetter
2020-04-08 12:15     ` [Intel-gfx] " Daniel Vetter

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=20200408084040.GA11347@jamwan02-TSP300 \
    --to=james.qian.wang@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=Mihail.Atanassov@arm.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nd@arm.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.