All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc: fix incorrect handling of the comparison arguments
Date: Thu, 26 Nov 2015 22:13:09 +0000	[thread overview]
Message-ID: <1448575918.2773.23.camel@synopsys.com> (raw)
In-Reply-To: <871tbctoxe.fsf@dell.be.48ers.dk>

Hi Peter,

On Thu, 2015-11-26 at 22:45 +0100, Peter Korsgaard wrote:
> > > > > > "Lada" == Lada Trimasova <Lada.Trimasova@synopsys.com> writes:
> 
> Hi,
> 
>  > This patch fixes compiler error during libbroadvoice build.
>  > The comparison arguments where not correctly handled.
>  > The fix is done in development tree:
>  > https://github.com/foss-for-synopsys-dwc-arc-processors/gcc/commit/b4035128ba8f8bbbf9527f54f261a87b304ca4c5
>  > and will be a part of the next release of ARC GNU tools.
>  > Once that new release happens this patch must be removed.
> 
>  > Fixes:
>  > http://autobuild.buildroot.net/results/bea/beace68a19382b43370c798dcf7d2ef412f9d75e/
> 
>  > Signed-off-by: Lada Trimasova <ltrimas@synopsys.com>
>  > Cc: Alexey Brodkin <abrodkin@synopsys.com>
>  > Cc: Anton Kolesov <akolesov@synopsys.com>
>  > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
>  > Cc: Peter Korsgaard <peter@korsgaard.com>
> 
> Alex/Anton, an acked-by would be good. Should this go into the 2015.11
> release?

I think it worth applying onto 2015.11 because this is a bugfix but not
new feature.

Acked-by: Alexey Brodkin <abrodkin@synopsys.com>

-Alexey

  reply	other threads:[~2015-11-26 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26 17:21 [Buildroot] [PATCH] gcc: fix incorrect handling of the comparison arguments Lada Trimasova
2015-11-26 21:45 ` Peter Korsgaard
2015-11-26 22:13   ` Alexey Brodkin [this message]
2015-11-26 22:27     ` Peter Korsgaard

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=1448575918.2773.23.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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.