From: "Christian König" <christian.koenig@amd.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Karolina Stolarek <karolina.stolarek@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, Huang Rui <ray.huang@amd.com>
Subject: Re: linux-next: Tree for Aug 17 (DRM_TTM KUNIT tests)
Date: Fri, 18 Aug 2023 07:32:31 +0200 [thread overview]
Message-ID: <02a565a0-9307-7620-7e53-f2630b97f0bd@amd.com> (raw)
In-Reply-To: <17065c3f-87bb-c2a9-e8f6-82fecd15b9c7@infradead.org>
Am 17.08.23 um 20:44 schrieb Randy Dunlap:
>
> On 8/16/23 21:47, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20230816:
>>
> on risc-v 32-bit:
> when
> # CONFIG_MMU is not set
Patch to fix this is already queued up for the next pull request.
Sorry for the noise,
Christian.
>
>
> WARNING: unmet direct dependencies detected for DRM_TTM
> Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && MMU [=n]
> Selected by [y]:
> - DRM_TTM_KUNIT_TEST [=y] && HAS_IOMEM [=y] && DRM [=y] && KUNIT [=y]
>
> WARNING: unmet direct dependencies detected for DRM_TTM
> Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && MMU [=n]
> Selected by [y]:
> - DRM_TTM_KUNIT_TEST [=y] && HAS_IOMEM [=y] && DRM [=y] && KUNIT [=y]
>
> WARNING: unmet direct dependencies detected for DRM_TTM
> Depends on [n]: HAS_IOMEM [=y] && DRM [=y] && MMU [=n]
> Selected by [y]:
> - DRM_TTM_KUNIT_TEST [=y] && HAS_IOMEM [=y] && DRM [=y] && KUNIT [=y]
>
> /opt/crosstool/gcc-13.1.0-nolibc/riscv32-linux/bin/riscv32-linux-ld: drivers/gpu/drm/ttm/ttm_bo_vm.o: in function `.L31':
> ttm_bo_vm.c:(.text+0x42c): undefined reference to `vmf_insert_pfn_prot'
> /opt/crosstool/gcc-13.1.0-nolibc/riscv32-linux/bin/riscv32-linux-ld: drivers/gpu/drm/ttm/ttm_bo_vm.o: in function `.L104':
> ttm_bo_vm.c:(.text+0xa70): undefined reference to `vmf_insert_pfn_prot'
>
>
prev parent reply other threads:[~2023-08-18 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 4:47 linux-next: Tree for Aug 17 Stephen Rothwell
2023-08-17 18:44 ` linux-next: Tree for Aug 17 (DRM_TTM KUNIT tests) Randy Dunlap
2023-08-18 5:32 ` 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=02a565a0-9307-7620-7e53-f2630b97f0bd@amd.com \
--to=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karolina.stolarek@intel.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--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).