From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Board defconfigs lacking maintainers
Date: Mon, 5 Mar 2018 15:59:54 +0100 [thread overview]
Message-ID: <20180305155954.1655ce43@windsurf.home> (raw)
In-Reply-To: <a838cf4c-612f-2af4-c5c3-25dc9d51d859@lucaceresoli.net>
Hello,
On Mon, 5 Mar 2018 15:35:27 +0100, Luca Ceresoli wrote:
> > If you are interested in one of the below defconfigs, could you please
> > send an update to the DEVELOPERS file to add yourself? Defconfigs not
> > associated to any developer are likely to be dropped at some point in
> > the future, since they will most likely fail to build due to toolchain
> > updates, and nobody will be there to fix those issues.
>
> What is required exactly to be considered a board maintainer? Ensure
> that it builds, or that it boots?
We don't have super strict rules. But defconfigs are meant to provide a
ready-to-use initial configuration. So if the configuration is not
ready-to-use because it doesn't boot, it isn't very useful.
So, IMO, we should only have defconfigs that are boot tested by someone.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-03-05 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 22:15 [Buildroot] Board defconfigs lacking maintainers Thomas Petazzoni
2018-03-05 7:50 ` daggs
2018-03-05 8:31 ` Thomas Petazzoni
2018-03-05 12:07 ` Adrian Perez de Castro
2018-03-05 12:37 ` Thomas Petazzoni
2018-03-07 13:41 ` Ezequiel Garcia
2018-03-07 14:04 ` Peter Korsgaard
2018-03-07 14:04 ` Thomas Petazzoni
2018-03-07 14:30 ` Ezequiel Garcia
2018-03-05 14:35 ` Luca Ceresoli
2018-03-05 14:59 ` Thomas Petazzoni [this message]
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=20180305155954.1655ce43@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