From: Rodrigo Siqueira Jordao <Rodrigo.Siqueira@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Melissa Wen <mwen@igalia.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Guenter Roeck <linux@roeck-us.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the amdgpu and powerpc-fixes trees
Date: Thu, 28 Jul 2022 16:36:56 -0400 [thread overview]
Message-ID: <ff2ea1b1-8039-369b-cc4c-b1d01d5cb02b@amd.com> (raw)
In-Reply-To: <CADnq5_OkWWO+hNz-n+bw5Wptn3JsfyuXe+ScXYTKwFz6JJf8fQ@mail.gmail.com>
Hi Stephen/Michael,
I made this fix:
https://patchwork.freedesktop.org/series/106824/
Could you check if it fixes the issue for you? If so, could you undo
your revert?
Thanks
Siqueira
On 2022-07-27 12:15, Alex Deucher wrote:
> + Rodrigo, Melissa
>
> On Wed, Jul 27, 2022 at 10:17 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>>> Hi all,
>>>
>>> After merging the amdgpu tree, today's linux-next build (powerpc
>>> allyesconfig) failed like this:
>>>
>>> ld: drivers/gpu/drm/amd/display/dc/dml/display_mode_lib.o uses hard float, drivers/gpu/drm/amd/display/dc/dcn30/dcn30_optc.o uses soft float
>>> ld: failed to merge target specific data of file drivers/gpu/drm/amd/display/dc/dcn30/dcn30_optc.o
>>>
>>> I have reverted commit
>>>
>>> c653c591789b ("drm/amdgpu: Re-enable DCN for 64-bit powerpc")
>>>
>>> for today.
>>
>> It bisects to:
>>
>> 40b31e5355ba ("drm/amd/display: Remove FPU flags from DCN30 Makefile")
>>
>> So I guess there's still some float code in dcn30?
>>
>> cheers
next prev parent reply other threads:[~2022-07-28 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 10:54 linux-next: build failure after merge of the amdgpu and powerpc-fixes trees Stephen Rothwell
2022-07-27 1:29 ` Michael Ellerman
2022-07-27 5:29 ` Stephen Rothwell
2022-07-27 14:17 ` Michael Ellerman
2022-07-27 16:15 ` Alex Deucher
2022-07-28 20:36 ` Rodrigo Siqueira Jordao [this message]
2022-07-28 22:51 ` Michael Ellerman
2022-07-28 2:11 ` Stephen Rothwell
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=ff2ea1b1-8039-369b-cc4c-b1d01d5cb02b@amd.com \
--to=rodrigo.siqueira@amd.com \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mpe@ellerman.id.au \
--cc=mwen@igalia.com \
--cc=sfr@canb.auug.org.au \
/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