From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] freescale_imx31_3stack_defconfig fails to build
Date: Mon, 5 Mar 2018 08:53:14 +0100 [thread overview]
Message-ID: <20180305085314.3ce92959@windsurf.home> (raw)
In-Reply-To: <CAOMZO5BntMxqEBPuXVs2CX2L9OWGrf-AzbsOUeDN8qqcJgS8cg@mail.gmail.com>
Hello,
On Sun, 4 Mar 2018 20:21:14 -0300, Fabio Estevam wrote:
> > See:
> >
> > https://gitlab.com/buildroot.org/buildroot/-/jobs/55306817
> >
> > Is one of you interested in maintaining/fixing this board ? If so,
> > could you fix it and also submit a patch to add yourself to the
> > DEVELOPERS file ?
>
> I can send a patch converting the defconfig to use a mainline kernel instead.
Would be good, thanks! Do you have a way of testing it, or you don't
have access to the HW platform ?
If nobody has access to the HW platform, I think we could just as well
drop the defconfig.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-03-05 7:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 21:55 [Buildroot] freescale_imx31_3stack_defconfig fails to build Thomas Petazzoni
2018-03-04 23:21 ` Fabio Estevam
2018-03-05 7:53 ` Thomas Petazzoni [this message]
2018-03-05 11:03 ` Fabio Estevam
2018-03-10 14:40 ` Fabio Estevam
2018-03-10 15:39 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2016-11-05 13:35 Thomas Petazzoni
2016-11-05 15:05 ` Fabio Estevam
2016-11-05 15:26 ` Thomas Petazzoni
2016-11-05 15:27 ` Fabio Estevam
[not found] ` <6234984d-6409-37c1-b050-504775d37c17@bergerie>
2016-11-05 16:16 ` Thomas Petazzoni
2016-11-05 16:37 ` Fabio Estevam
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=20180305085314.3ce92959@windsurf.home \
--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