From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] configs: atmel: at91sam9260eknf: update defconfig
Date: Wed, 9 Nov 2016 12:08:21 +0100 [thread overview]
Message-ID: <20161109120821.3ee13355@free-electrons.com> (raw)
In-Reply-To: <20161109103955.qgeomymgonuoyxu5@rfolt0960.corp.atmel.com>
Hello,
On Wed, 9 Nov 2016 11:39:55 +0100, Ludovic Desroches wrote:
> > If you are not able/willing to test those defconfigs, then we could
> > just as well remove them. But I'm not going to merge a defconfig that
> > doesn't comply with our policy of having a fixed kernel and a fixed
> > bootloader version.
>
> Can I use a fixed version of the compiler too? It seems it makes sense
> because this defconfig was tested but is no more compiling.
This could be an option indeed (reverting to gcc 4.x instead of gcc
5.x). However, the fact that no-one is willing to test/maintain this
defconfig is a sign that nobody is interested in it. So I'd rather
remove it, than keep a defconfig that gets never updated, even when
there is a build issue.
So, options are clear:
1. Remove the defconfig entirely.
2. Update the defconfig in the proper way, minimally tested on HW.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-09 11:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 6:59 [Buildroot] [PATCH 0/4] configs: atmel: update of old boards Ludovic Desroches
2016-11-09 6:59 ` [Buildroot] [PATCH 1/4] configs: atmel: at91sam9260eknf: update defconfig Ludovic Desroches
2016-11-09 7:36 ` Baruch Siach
2016-11-09 9:52 ` Alexandre Belloni
2016-11-09 10:00 ` Baruch Siach
2016-11-09 10:12 ` Alexandre Belloni
2016-11-09 10:15 ` Ludovic Desroches
2016-11-09 10:10 ` Ludovic Desroches
2016-11-09 10:25 ` Thomas Petazzoni
2016-11-09 10:39 ` Ludovic Desroches
2016-11-09 11:08 ` Thomas Petazzoni [this message]
2016-11-09 6:59 ` [Buildroot] [PATCH 2/4] configs: atmel: at91sam9rlek: " Ludovic Desroches
2016-11-09 6:59 ` [Buildroot] [PATCH 3/4] configs: atmel: at91sam9g20dfc: " Ludovic Desroches
2016-11-09 6:59 ` [Buildroot] [PATCH 4/4] configs: atmel: at91sam9g45m10ek: " Ludovic Desroches
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=20161109120821.3ee13355@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 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.