All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	"Siqueira, Rodrigo" <Rodrigo.Siqueira@amd.com>,
	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: Wed, 27 Jul 2022 12:15:01 -0400	[thread overview]
Message-ID: <CADnq5_OkWWO+hNz-n+bw5Wptn3JsfyuXe+ScXYTKwFz6JJf8fQ@mail.gmail.com> (raw)
In-Reply-To: <87leseabci.fsf@mpe.ellerman.id.au>

+ 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

  reply	other threads:[~2022-07-27 16:15 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 [this message]
2022-07-28 20:36     ` Rodrigo Siqueira Jordao
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=CADnq5_OkWWO+hNz-n+bw5Wptn3JsfyuXe+ScXYTKwFz6JJf8fQ@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=Rodrigo.Siqueira@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.