linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Qiang Yu <yuq825@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	kbuild-all@01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Manfred Spraul <manfred@colorfullife.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	lima@lists.freedesktop.org,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [mmotm:master 227/248] lima_gem.c:undefined reference to `vmf_insert_mixed'
Date: Sun, 7 Apr 2019 21:44:18 -0700	[thread overview]
Message-ID: <162043bc-a3c6-f5d6-f073-c52b1c5ec8b9@infradead.org> (raw)
In-Reply-To: <CAKGbVbsFXvEjxNH7Wm5Qr8ODyDfJ438qRELn0AB1BJdVV1AK6Q@mail.gmail.com>

On 4/7/19 6:30 PM, Qiang Yu wrote:
> Thanks Randy, I can add these.
> 
> Where should I send/submit the patch to in this case? Still drm-misc?

Sounds good to me.

Thanks.

> Regards,
> Qiang
> 
> 
> On Mon, Apr 8, 2019 at 3:08 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>
>> On 4/5/19 11:47 PM, kbuild test robot wrote:
>>> Hi Andrew,
>>>
>>> It's probably a bug fix that unveils the link errors.
>>>
>>> tree:   git://git.cmpxchg.org/linux-mmotm.git master
>>> head:   b09c000f671826e6f073a7f89b266e4ac998952b
>>> commit: 39a08f353e1f30f7ba2e8b751a9034010a99666c [227/248] linux-next-git-rejects
>>> config: sh-allyesconfig (attached as .config)
>>> compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
>>> reproduce:
>>>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>>         chmod +x ~/bin/make.cross
>>>         git checkout 39a08f353e1f30f7ba2e8b751a9034010a99666c
>>>         # save the attached .config to linux build tree
>>>         GCC_VERSION=7.2.0 make.cross ARCH=sh
>>>
>>> All errors (new ones prefixed by >>):
>>>
>>>    arch/sh/kernel/cpu/sh2/clock-sh7619.o:(.data+0x1c): undefined reference to `followparent_recalc'
>>>    drivers/gpu/drm/lima/lima_gem.o: In function `lima_gem_fault':
>>>>> lima_gem.c:(.text+0x6c): undefined reference to `vmf_insert_mixed'
>>
>>
>> vmf_insert_mixed() is only built for MMU configs, and the attached config
>> does not set/enable MMU.
>> Maybe this driver should depend on MMU, like several other drm drivers do.
>>
>>
>> Also, lima_gem.c needs this line to be added to it:
>>
>> --- mmotm-2019-0405-1828.orig/drivers/gpu/drm/lima/lima_gem.c
>> +++ mmotm-2019-0405-1828/drivers/gpu/drm/lima/lima_gem.c
>> @@ -1,6 +1,7 @@
>>  // SPDX-License-Identifier: GPL-2.0 OR MIT
>>  /* Copyright 2017-2019 Qiang Yu <yuq825@gmail.com> */
>>
>> +#include <linux/mm.h>
>>  #include <linux/sync_file.h>
>>  #include <linux/pfn_t.h>
>>
>>
>>
>> --
>> ~Randy
> 


-- 
~Randy


      reply	other threads:[~2019-04-08  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-06  6:47 [mmotm:master 227/248] lima_gem.c:undefined reference to `vmf_insert_mixed' kbuild test robot
2019-04-07 19:08 ` Randy Dunlap
2019-04-08  1:30   ` Qiang Yu
2019-04-08  4:44     ` 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=162043bc-a3c6-f5d6-f073-c52b1c5ec8b9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=lima@lists.freedesktop.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=manfred@colorfullife.com \
    --cc=yuq825@gmail.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 NNTP newsgroup(s).