Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Legacy patches for Binutils?
Date: Fri, 19 Oct 2018 14:55:59 +0200	[thread overview]
Message-ID: <20181019145559.320c2946@windsurf> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE646817718F@DE02WEMBXB.internal.synopsys.com>

Hello,

On Fri, 19 Oct 2018 12:53:11 +0000, Alexey Brodkin wrote:

> > I don't have anything specific thought, but I share the general feeling
> > that the stack of patches we have on binutils should be
> > analyzed/revisited, as I'm also sure that a number of those patches are
> > no longer needed.  
> 
> Should I add this as a topic for the meeting?

The topics we write down for the meeting are more discussion topics.
Here I don't think there's much discussion needed: simply someone need
to look at those patches, their history, the binutils source code, and
decide if they are still needed or not. I don't think there is anything
controversial here.

However, the meeting is also a moment for hacking, so it's definitely
something you can pick up as a "fun" task to achieve during the
meeting :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-19 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 12:24 [Buildroot] Legacy patches for Binutils? Alexey Brodkin
2018-10-19 12:36 ` Romain Naour
2018-10-19 12:37 ` Thomas Petazzoni
2018-10-19 12:53   ` Alexey Brodkin
2018-10-19 12:55     ` Thomas Petazzoni [this message]
2018-10-19 12:57       ` Romain Naour

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=20181019145559.320c2946@windsurf \
    --to=thomas.petazzoni@bootlin.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