All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain: Fix toolchain to create proper builds for MIPS XBurst targets
Date: Fri, 5 Jan 2018 21:27:15 +0100	[thread overview]
Message-ID: <20180105212715.5e50d391@windsurf> (raw)
In-Reply-To: <1515170305-25742-1-git-send-email-johannes.schmitz1@gmail.com>

Hello,

This is PATCH 2/2, we haven't received PATCH 1/2 in the mailing list.
Where is it?

On Fri,  5 Jan 2018 17:38:25 +0100, Johannes Schmitz wrote:
> This patch is need for example for ci20, -mfused-madd is deprecated, we
> need to use -ffp-contract instead.
> 
> This is basically a resubmission of
> https://patchwork.ozlabs.org/patch/800406/
> 
> Please consider accepting the original patch, otherwise buildroot is
> basically broken for ci20 and similar platforms.

Is your patch a resubmission, or an additional patch ? You say it's a
resubmission, and then the next paragraph you say we should also apply
the original patch.

Also, the commit log should explain since which gcc version is
-mfused-madd deprecated, and since which gcc version is -ffp-contract
available.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2018-01-05 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 16:38 [Buildroot] [PATCH 2/2] toolchain: Fix toolchain to create proper builds for MIPS XBurst targets Johannes Schmitz
2018-01-05 20:27 ` Thomas Petazzoni [this message]
2018-01-05 21:34   ` Johannes Schmitz
2018-01-06 14:16     ` Thomas Petazzoni

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=20180105212715.5e50d391@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.