From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] configs: atmel: at91sam9260eknf: update defconfig
Date: Wed, 9 Nov 2016 12:00:27 +0200 [thread overview]
Message-ID: <20161109100027.yqe6ilsxofi2t4ey@tarshish> (raw)
In-Reply-To: <20161109095249.bgurrb6bhujkgnac@piout.net>
Hi Alexandre,
On Wed, Nov 09, 2016 at 10:52:49AM +0100, Alexandre Belloni wrote:
> On 09/11/2016 at 09:36:38 +0200, Baruch Siach wrote :
> > On Wed, Nov 09, 2016 at 07:59:45AM +0100, Ludovic Desroches wrote:
> > > # 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.
>
> I'm not sure this is actually useful because the amount of testing is
> minimal and it just increases the maintenance burden.
I don't understand. How would locking a specific kernel version in the
defconfig increase maintenance burden? Any tested kernel version would do. We
just want to ensure consistent user experience. Otherwise the built kernel
will change with the default value of BR2_LINUX_KERNEL_VERSION.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-11-09 10:00 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 [this message]
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
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=20161109100027.yqe6ilsxofi2t4ey@tarshish \
--to=baruch@tkos.co.il \
--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.