From: "Maíra Canal" <mcanal@igalia.com>
To: "Maíra Canal" <mcanal@igalia.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Melissa Wen" <mwen@igalia.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/vgem: Drop struct drm_vgem_gem_object
Date: Mon, 20 Mar 2023 16:07:15 -0300 [thread overview]
Message-ID: <865a2a60-1e2a-9e9b-3da1-d58da3a9de6b@igalia.com> (raw)
In-Reply-To: <20230222160617.171429-1-mcanal@igalia.com>
On 2/22/23 13:06, Maíra Canal wrote:
> Commit 45d9c8dde4cd ("drm/vgem: use shmem helpers") introduced shmem
> helpers to vgem and with that, removed all uses of the struct
> drm_vgem_gem_object. So, as the struct is no longer used, delete it.
>
> Signed-off-by: Maíra Canal <mcanal@igalia.com>
> ---
Applied to drm-misc-next.
Best Regards,
- Maíra Canal
> drivers/gpu/drm/vgem/vgem_drv.h | 11 -----------
> 1 file changed, 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/vgem/vgem_drv.h b/drivers/gpu/drm/vgem/vgem_drv.h
> index 0ed300317f87..34cf63e6fb3d 100644
> --- a/drivers/gpu/drm/vgem/vgem_drv.h
> +++ b/drivers/gpu/drm/vgem/vgem_drv.h
> @@ -39,17 +39,6 @@ struct vgem_file {
> struct mutex fence_mutex;
> };
>
> -#define to_vgem_bo(x) container_of(x, struct drm_vgem_gem_object, base)
> -struct drm_vgem_gem_object {
> - struct drm_gem_object base;
> -
> - struct page **pages;
> - unsigned int pages_pin_count;
> - struct mutex pages_lock;
> -
> - struct sg_table *table;
> -};
> -
> int vgem_fence_open(struct vgem_file *file);
> int vgem_fence_attach_ioctl(struct drm_device *dev,
> void *data,
prev parent reply other threads:[~2023-03-20 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 16:06 [PATCH] drm/vgem: Drop struct drm_vgem_gem_object Maíra Canal
2023-03-15 22:31 ` Melissa Wen
2023-03-20 19:07 ` Maíra Canal [this message]
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=865a2a60-1e2a-9e9b-3da1-d58da3a9de6b@igalia.com \
--to=mcanal@igalia.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=mwen@igalia.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).