dri-devel Archive mirror
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: Zack Rusin <zackr@vmware.com>, dri-devel@lists.freedesktop.org
Cc: Martin Krastev <krastevm@vmware.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH 9/9] drm/vmwgfx: Fix implicit declaration error
Date: Wed, 9 Jun 2021 19:24:25 +0200	[thread overview]
Message-ID: <5650bbe1-06fd-3992-ac0c-be27184ab39f@amd.com> (raw)
In-Reply-To: <20210609172307.131929-10-zackr@vmware.com>



Am 09.06.21 um 19:23 schrieb Zack Rusin:
> The declarations of ttm_range_man_init and ttm_range_man_fini
> have been moved to ttm_range_manager.h so we have to add it
> to the include list.
>
> Signed-off-by: Zack Rusin <zackr@vmware.com>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Fixes: 3eb7d96e9415 ("drm/ttm: flip over the range manager to self allocated nodes")
> Cc: Christian König <christian.koenig@amd.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Reviewed-by: Martin Krastev <krastevm@vmware.com>

Reviewed-by: Christian König <christian.koenig@amd.com>

Sorry for the noise.

> ---
>   drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> index d51f215bd715..48a62fb0da2f 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
> @@ -36,6 +36,7 @@
>   #include <drm/drm_ioctl.h>
>   #include <drm/drm_sysfs.h>
>   #include <drm/ttm/ttm_bo_driver.h>
> +#include <drm/ttm/ttm_range_manager.h>
>   #include <drm/ttm/ttm_placement.h>
>   #include <generated/utsrelease.h>
>   


      reply	other threads:[~2021-06-09 17:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 17:22 [PATCH 0/9] Adding support for mks-stats and some cleanups/fixes Zack Rusin
2021-06-09 17:22 ` [PATCH 1/9] drm/vmwgfx: Simplify devcaps code Zack Rusin
2021-06-09 17:23 ` [PATCH 2/9] drm/vmwgfx: Introduce VMware mks-guest-stats Zack Rusin
2021-06-09 17:23 ` [PATCH 3/9] drm/vmwgfx: Fix subresource updates with new contexts Zack Rusin
2021-06-10  6:49   ` Thomas Hellström (Intel)
2021-06-10 16:59     ` Zack Rusin
2021-06-09 17:23 ` [PATCH 4/9] drm/vmwgfx: Fix some static checker warnings Zack Rusin
2021-06-09 17:23 ` [PATCH 5/9] drm/vmwgfx: remove code that was using physical page addresses Zack Rusin
2021-06-09 17:23 ` [PATCH 6/9] drm/vmwgfx: inline access to the pages from the piter Zack Rusin
2021-06-09 17:23 ` [PATCH 7/9] drm/vmwgfx: Refactor vmw_mksstat_remove_ioctl to expect pgid match with vmw_mksstat_add_ioctl to authorise removal Zack Rusin
2021-06-09 17:23 ` [PATCH 8/9] drm/vmwgfx: Remove vmw_chipset Zack Rusin
2021-06-09 17:23 ` [PATCH 9/9] drm/vmwgfx: Fix implicit declaration error Zack Rusin
2021-06-09 17:24   ` Christian König [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=5650bbe1-06fd-3992-ac0c-be27184ab39f@amd.com \
    --to=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=krastevm@vmware.com \
    --cc=matthew.auld@intel.com \
    --cc=rdunlap@infradead.org \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).