Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Add go language support
Date: Wed, 2 Mar 2016 23:54:28 +0100	[thread overview]
Message-ID: <20160302235428.205fa042@free-electrons.com> (raw)
In-Reply-To: <1456958592.13916.50.camel@infradead.org>

Geoff,

On Wed, 02 Mar 2016 14:43:12 -0800, Geoff Levand wrote:

> On Wed, 2016-03-02 at 23:18 +0100, Thomas Petazzoni wrote:
> > I took a quick look at this.  Patch 1, which builds the go
> > > complier, has the bootstrap and final compiler built in the
> > > same package.  I think it better to split the bootstrap out
> > > into its own package as I have done since then the two packages
> > > are each then simpler and I think easier to maintain.
> > 
> > I'll have a look at this specific aspect. Having two packages that use
> > the same source is not always the best solution, but I'll have a look.
> 
> Just to mention it, the two use different source versions, 1.4.3
> for the bootstrap, and 1.5.3 (currently) for the final compiler.

Yeah, I just discovered this while reviewing your patches. In this
case, it definitely makes sense. I forgot that the 1.5 Go compiler had
some parts of it in Go, and therefore needed a previous Go compiler.

> > > OK. As I said, what I would like to see is one single patch series that
> > contains the full support, and that is approved by the interested
> > parties (you, Ludovic and Christian). The Buildroot maintainers cannot
> > be expert in all topics, and diving into the Go topic would require
> > quite some time. So I'd like to see a single patch series acknowledged
> > by all parties so that we can have some good confidence that it does
> > things the right way.
> > 
> > Of course, it can also be two separate patch series: one from you with
> > the core Go stuff (acknowledged by Christian and Ludovic), and another
> > from Ludovic with the Go package infrastructure (acknowledged by you
> > and Christian).
> 
> I understand your need to have these things reviewed by the interested
> parties.  I will work towards the consensus.

Thanks a lot!

On my side, I reviewed your patches. There are a few comments/issues,
but nothing major. Overall it looks fairly simple and straightforward.

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

  reply	other threads:[~2016-03-02 22:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 19:23 [Buildroot] [PATCH 0/4] Add go language support Geoff Levand
2016-03-02 19:23 ` [Buildroot] [PATCH 3/4] Add go target support Geoff Levand
2016-03-02 22:51   ` Thomas Petazzoni
2016-03-03  1:11     ` Geoff Levand
2016-03-02 19:23 ` [Buildroot] [PATCH 1/4] Add package go-bootstrap Geoff Levand
2016-03-02 22:43   ` Thomas Petazzoni
2016-03-03  1:11     ` Geoff Levand
2016-03-03  8:15       ` Thomas Petazzoni
2016-03-02 19:23 ` [Buildroot] [PATCH 4/4] Add package flannel Geoff Levand
2016-03-02 22:53   ` Thomas Petazzoni
2016-03-03  1:11     ` Geoff Levand
2016-03-02 19:23 ` [Buildroot] [PATCH 2/4] Add go host support Geoff Levand
2016-03-02 22:50   ` Thomas Petazzoni
2016-03-03  1:11     ` Geoff Levand
2016-03-02 20:49 ` [Buildroot] [PATCH 0/4] Add go language support Thomas Petazzoni
2016-03-02 21:47   ` Geoff Levand
2016-03-02 21:52     ` Christian Stewart
2016-03-02 22:31       ` Geoff Levand
2016-03-02 22:40         ` Christian Stewart
2016-03-21 16:32           ` Geoff Levand
2016-03-22 18:09             ` Christian Stewart
2016-03-02 22:18     ` Thomas Petazzoni
2016-03-02 22:43       ` Geoff Levand
2016-03-02 22:54         ` Thomas Petazzoni [this message]
2016-03-03  1:09           ` Geoff Levand

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=20160302235428.205fa042@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox