public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	dri-devel <dri-devel@lists•freedesktop.org>,
	VMware Graphics <linux-graphics-maintainer@vmware•com>,
	Roland Scheidegger <sroland@vmware•com>,
	Zack Rusin <zackr@vmware•com>
Subject: Re: linux-next: Tree for Jun 28 (drm/vmwgfx/)
Date: Mon, 28 Jun 2021 08:53:08 -0700	[thread overview]
Message-ID: <e99431bc-676e-29a6-e6ee-ea5fa18f0ea4@infradead.org> (raw)
In-Reply-To: <20210628205732.4c2a0abf@canb.auug.org.au>

On 6/28/21 3:57 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20210625:
> 

on i386 or 86_64:

../drivers/gpu/drm/vmwgfx/vmwgfx_drv.c: In function 'vmw_vram_manager_init':
../drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:678:8: error: implicit declaration of function 'ttm_range_man_init'; did you mean 'ttm_tt_mgr_init'? [-Werror=implicit-function-declaration]
  ret = ttm_range_man_init(&dev_priv->bdev, TTM_PL_VRAM, false,
        ^~~~~~~~~~~~~~~~~~
        ttm_tt_mgr_init
../drivers/gpu/drm/vmwgfx/vmwgfx_drv.c: In function 'vmw_vram_manager_fini':
../drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:690:2: error: implicit declaration of function 'ttm_range_man_fini'; did you mean 'ttm_pool_mgr_fini'? [-Werror=implicit-function-declaration]
  ttm_range_man_fini(&dev_priv->bdev, TTM_PL_VRAM);
  ^~~~~~~~~~~~~~~~~~
  ttm_pool_mgr_fini


The randconfig seed for this build is:
KCONFIG_SEED=0x96D160F4

or do you want the full randconfig file?


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead•org>


      reply	other threads:[~2021-06-28 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 10:57 linux-next: Tree for Jun 28 Stephen Rothwell
2021-06-28 15:53 ` Randy Dunlap [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=e99431bc-676e-29a6-e6ee-ea5fa18f0ea4@infradead.org \
    --to=rdunlap@infradead$(echo .)org \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=linux-graphics-maintainer@vmware$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=sroland@vmware$(echo .)com \
    --cc=zackr@vmware$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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