Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] gcc: explicitly use C{XX}FLAGS_FOR_TARGET instead of --enable-target-optspace
Date: Tue, 21 Apr 2015 13:43:53 +0000	[thread overview]
Message-ID: <1429623833.2624.15.camel@synopsys.com> (raw)
In-Reply-To: <20140923131924.2334adec@free-electrons.com>

Hi Thomas,

On Tue, 2014-09-23 at 13:19 +0200, Thomas Petazzoni wrote:
> Dear Alexey Brodkin,
> 
> On Tue, 23 Sep 2014 11:10:16 +0000, Alexey Brodkin wrote:
> 
> > > > I'm wondering if this version is fine and we may go ahead an apply it?
> > > 
> > > Please treat this as a polite reminder about this pending patch.
> > 
> > Any chance for this change to made its way into upstream Buildroot?
> 
> Yes. Please give us some time to test it before applying it. It's
> touching a fairly sensitive area, so we don't apply such patches
> lightly.
> 
> Best regards,
> 
> Thomas

I just got a reminder on my pending patches in Buildroot so I'm updating
that one.

This v4 patch should be dropped because it is now superseded with v5
(http://patchwork.ozlabs.org/patch/453849/) which in its turn is just a
rebase of v4 on top of more up to date master.

-Alexey

  parent reply	other threads:[~2015-04-21 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01  7:55 [Buildroot] [PATCH v4] gcc: explicitly use C{XX}FLAGS_FOR_TARGET instead of --enable-target-optspace Alexey Brodkin
2014-09-08  5:53 ` Alexey Brodkin
2014-09-15 13:29   ` Alexey Brodkin
2014-09-23 11:10     ` Alexey Brodkin
2014-09-23 11:19       ` Thomas Petazzoni
2014-09-23 11:24         ` Alexey Brodkin
2015-04-21 13:43         ` Alexey Brodkin [this message]
2015-04-21 16:25           ` Baruch Siach
2015-04-21 17:04             ` Alexey Brodkin

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=1429623833.2624.15.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox