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 1/4] configs: atmel: at91sam9260eknf: update defconfig
Date: Wed, 9 Nov 2016 11:25:50 +0100	[thread overview]
Message-ID: <20161109112550.36c1ec17@free-electrons.com> (raw)
In-Reply-To: <20161109101009.l66iviomyfuit2t5@rfolt0960.corp.atmel.com>

Hello,

On Wed, 9 Nov 2016 11:10:09 +0100, Ludovic Desroches wrote:

> > Why enable both U-Boot and Barebox?
> >   
> 
> I don't know why Barebox was selected but the 'official' bootloader is
> U-Boot for all our products that's why I add it. I kept Barebox because
> it was already selected and I don't know if someone is still using it or
> not.

But the end result is a defconfig that doesn't make any sense.

Please provide a defconfig that makes sense, and with an updated
readme.txt if you decide to change the bootloader (and therefore the
flashing instructions).

> > >  # Kernel
> > >  BR2_LINUX_KERNEL=y
> > > -BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> > > -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="3.9.1"  
> > 
> > For the sake of reproducibility you should set this to the version you tested, 
> > say, 4.8.6. The same goes for other patches in this series.
> 
> As Alexandre said, we don't want to spend time for the maintainance of these
> old boards so sticking to the mainline seems to be the way to go. Giving a
> version is a kind of commitment but we no longer perform tests on these
> boards excepting kernel boot with kernelci.

That's not Buildroot policy. We want defconfigs with fixed kernel and
bootloader versions, so that we know they have been tested.

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.

Best regards,

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

  reply	other threads:[~2016-11-09 10:25 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 [this message]
2016-11-09 10:39         ` Ludovic Desroches
2016-11-09 11:08           ` Thomas Petazzoni
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=20161109112550.36c1ec17@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