All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Board defconfigs lacking maintainers
Date: Wed, 7 Mar 2018 15:04:18 +0100	[thread overview]
Message-ID: <20180307150418.4b19ba57@windsurf> (raw)
In-Reply-To: <CAAEAJfB-D3FFVrWdxkb2ENciYj=YpP4qSKwxd1NDLzgfFTrLnA@mail.gmail.com>

Hello,

On Wed, 7 Mar 2018 10:41:37 -0300, Ezequiel Garcia wrote:

> >> One if my work colleagues has a ci20 around which I *think* he has been using
> >> mostly with Buildroot as the base system. I'll get to him and see whether it
> >> may be possible for one of us to adopt this one.  
> >
> > Great! This defconfig was initially contributed by Vicente Olivert
> > Riera, but he has left Imagination Technologies, so he is no longer
> > working on Buildroot or MIPS.
> >  
> 
> Should nobody adopt Ci20, I will. I'm working on it as pet project.

Please submit a patch to the DEVELOPERS file then :-)

The ci20_defconfig build is currently broken, due to MIPS gcc flags
issues. A patch has been submitted, but we haven't merged it yet.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com

  parent reply	other threads:[~2018-03-07 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 22:15 [Buildroot] Board defconfigs lacking maintainers Thomas Petazzoni
2018-03-05  7:50 ` daggs
2018-03-05  8:31   ` Thomas Petazzoni
2018-03-05 12:07 ` Adrian Perez de Castro
2018-03-05 12:37   ` Thomas Petazzoni
2018-03-07 13:41     ` Ezequiel Garcia
2018-03-07 14:04       ` Peter Korsgaard
2018-03-07 14:04       ` Thomas Petazzoni [this message]
2018-03-07 14:30         ` Ezequiel Garcia
2018-03-05 14:35 ` Luca Ceresoli
2018-03-05 14:59   ` 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=20180307150418.4b19ba57@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 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.