From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>,
Roberto Medina <robertoxmed@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1 v3] configs/roc_rk3399_pc: Bring back and update the configuration for the rockchip rk3399 built by firefly.
Date: Sat, 12 Aug 2023 22:00:22 +0200 [thread overview]
Message-ID: <20230812220022.4a43443d@windsurf> (raw)
In-Reply-To: <2696013.mvXUDI8C0e@kilian-aisec>
On Fri, 11 Aug 2023 23:59:11 +0200
Kilian Zinnecker via buildroot <buildroot@buildroot.org> wrote:
> > Actually in v2 of this patch, Thomas requested to set a fixed version
> > for U-Boot (mail from 08/08). Which made sense to me as TFA and Linux
> > have a fixed version as well.
>
> Ah, I see, makes sense ... then never mind my comment :)
Correct, our convention in defconfigs is that the version of the Linux
kernel and bootloader/firmware should be fixed. Indeed, we want the
defconfigs to be known working configurations, that have been tested on
hardware. If we let them the default/latest Linux/U-Boot version, it
means this version gets auto-updated, without the defconfig maintainer
necessarily checking that it is still works OK on HW.
So: policy is to use fixed version for Linux kernel and bootloaders in
defconfigs.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-12 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 16:25 [Buildroot] [PATCH 0/1 v3] onfigs/roc_rk3399_pc: Bring back and update the configuration for the rockchip rk3399 built by firefly Roberto Medina
2023-08-11 16:25 ` [Buildroot] [PATCH 1/1 v3] configs/roc_rk3399_pc: " Roberto Medina
2023-08-11 19:02 ` Kilian Zinnecker via buildroot
2023-08-11 19:07 ` Kilian Zinnecker via buildroot
2023-08-11 20:59 ` Roberto Medina
2023-08-11 21:59 ` Kilian Zinnecker via buildroot
2023-08-12 20:00 ` Thomas Petazzoni via buildroot [this message]
2023-08-12 19:58 ` Thomas Petazzoni via buildroot
2023-08-12 20:22 ` Roberto Medina
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=20230812220022.4a43443d@windsurf \
--to=buildroot@buildroot.org \
--cc=kilian.zinnecker@mail.de \
--cc=robertoxmed@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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