linux-kernel - Re: linux-next: build failure after merge of the drm-misc tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 30 Oct 2020 08:53:26 +0100
From:   Christian König <christian.koenig@....com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        DRI <dri-devel@...ts.freedesktop.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the drm-misc tree

Am 30.10.20 um 01:07 schrieb Stephen Rothwell:
> Hi all,
>
> After merging the drm-misc tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpu/drm/nouveau/nouveau_ttm.c: In function 'nouveau_ttm_init':
> drivers/gpu/drm/nouveau/nouveau_ttm.c:320:19: error: implicit declaration of function 'swiotlb_nr_tbl' [-Werror=implicit-function-declaration]
>    320 |  need_swiotlb = !!swiotlb_nr_tbl();
>        |                   ^~~~~~~~~~~~~~

Mhm, thanks for the note. Looks like there is some merge conflict to me.

In my tree there is an "#if IS_ENABLED(CONFIG_SWIOTLB) && 
IS_ENABLED(CONFIG_X86)" around that line making sure the function is 
available.

Going to take a look later today.

Christian.

> Caused by commit
>
>    ee5d2a8e549e ("drm/ttm: wire up the new pool as default one v2")
>
> I have used the drm-misc tree from next-20201029 for today.
>