From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>, Dave Airlie <airlied@linux.ie>
Cc: Alex Deucher <alexdeucher@gmail.com>,
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 12:11:09 +1000 [thread overview]
Message-ID: <20220728121109.0cf6cb51@canb.auug.org.au> (raw)
In-Reply-To: <87leseabci.fsf@mpe.ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi all,
On Thu, 28 Jul 2022 00:17:49 +1000 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
> >
> > 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?
I have reverted commit 40b31e5355ba from the merge of the drm tree today (since
it has been merged in there) instead of commit c653c591789b.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
prev parent reply other threads:[~2022-07-28 2:11 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
2022-07-28 22:51 ` Michael Ellerman
2022-07-28 2:11 ` Stephen Rothwell [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=20220728121109.0cf6cb51@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@linux.ie \
--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 \
/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