From: "Christian König" <christian.koenig@amd.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
daniel@ffwll.ch, airlied@linux.ie, zackr@vmware.com,
linux-graphics-maintainer@vmware.com, ray.huang@amd.com,
mripard@kernel.org, maarten.lankhorst@linux.intel.com
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/ttm: Don't include drm_hashtab.h
Date: Mon, 15 Nov 2021 14:28:10 +0100 [thread overview]
Message-ID: <2b2eb217-3a7e-5f66-ee97-7b222ff2086a@amd.com> (raw)
In-Reply-To: <20211115125539.1730-2-tzimmermann@suse.de>
Am 15.11.21 um 13:55 schrieb Thomas Zimmermann:
> Remove the include statement for drm_hashtab.h. It's not required
> by TTM.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Reviewed-by: Christian König <christian.koenig@amd.com>
> ---
> include/drm/ttm/ttm_bo_api.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/include/drm/ttm/ttm_bo_api.h b/include/drm/ttm/ttm_bo_api.h
> index cd785cfa3123..c17b2df9178b 100644
> --- a/include/drm/ttm/ttm_bo_api.h
> +++ b/include/drm/ttm/ttm_bo_api.h
> @@ -32,7 +32,6 @@
> #define _TTM_BO_API_H_
>
> #include <drm/drm_gem.h>
> -#include <drm/drm_hashtab.h>
> #include <drm/drm_vma_manager.h>
> #include <linux/kref.h>
> #include <linux/list.h>
next prev parent reply other threads:[~2021-11-15 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 12:55 [PATCH 0/3] drm: Make DRM hashtable legacy Thomas Zimmermann
2021-11-15 12:55 ` [PATCH 1/3] drm/ttm: Don't include drm_hashtab.h Thomas Zimmermann
2021-11-15 13:28 ` Christian König [this message]
2021-11-15 12:55 ` [PATCH 2/3] drm/vmwgfx: Copy DRM hash-table code into driver Thomas Zimmermann
2021-11-15 14:33 ` Daniel Vetter
2021-11-15 16:27 ` Sam Ravnborg
2021-11-16 9:11 ` Thomas Zimmermann
2021-11-15 17:00 ` Zack Rusin
2021-11-16 9:20 ` Thomas Zimmermann
2021-11-15 12:55 ` [PATCH 3/3] drm: Declare hashtable as legacy Thomas Zimmermann
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=2b2eb217-3a7e-5f66-ee97-7b222ff2086a@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ray.huang@amd.com \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.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.