[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPM=9txaQ43GwOzXSE3prTRLbMt+ip=s_ssmFzWsfsTYdLssaw@mail.gmail.com>
Date: Tue, 25 Jun 2019 13:59:17 +1000
From: Dave Airlie <airlied@...il.com>
To: Nathan Chancellor <natechancellor@...il.com>
Cc: Anthony Koo <Anthony.Koo@....com>,
Alex Deucher <alexander.deucher@....com>,
Jun Lei <Jun.Lei@....com>,
Bhawanpreet Lakha <Bhawanpreet.Lakha@....com>,
Harry Wentland <harry.wentland@....com>,
Leo Li <sunpeng.li@....com>,
Christian König <christian.koenig@....com>,
"David (ChunMing) Zhou" <David1.Zhou@....com>,
amd-gfx mailing list <amd-gfx@...ts.freedesktop.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: arm32 build failure after abe882a39a9c ("drm/amd/display: fix
issue with eDP not detected on driver load")
Hi Alex,
please resolve this ASAP, I cannot pull your tree without this fixed
as it breaks my arm builds here.
an 8 second delay there seems pointless and arbitary, an 8 sec delay
there without a comment, seems like a lack of review.
Dave.
On Tue, 18 Jun 2019 at 11:12, Nathan Chancellor
<natechancellor@...il.com> wrote:
>
> Hi all,
>
> After commit abe882a39a9c ("drm/amd/display: fix issue with eDP not
> detected on driver load") in -next, arm32 allyesconfig builds start
> failing at link time:
>
> arm-linux-gnueabi-ld: drivers/gpu/drm/amd/display/dc/core/dc_link.o: in
> function `dc_link_detect':
> dc_link.c:(.text+0x260c): undefined reference to `__bad_udelay'
>
> arm32 only allows a udelay value of up to 2000, see
> arch/arm/include/asm/delay.h for more info.
>
> Please look into this when you have a chance!
> Nathan
Powered by blists - more mailing lists