From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Merge and reformat boards.cfg and MAINTAINERS
Date: Thu, 19 Sep 2013 08:29:49 +0200 [thread overview]
Message-ID: <20130919082949.1ea52c7f@lilith> (raw)
In-Reply-To: <20130917095500.738E.AA925319@jp.panasonic.com>
Hi Masahiro,
On Tue, 17 Sep 2013 09:55:00 +0900, Masahiro Yamada
<yamada.m@jp.panasonic.com> wrote:
> Hello Albert, Tom.
>
>
> Commit 27af930e9 added Active/Orphan status in the first column of boards.cfg.
>
> Could you tell the definition of "Active" and "Orphan".
>
>
> At first I imagined Orphan means a board without maintainer.
> But the maintainer information is missing from lots of Active boards.
> So I could not find the difference between Active and Orphan.
I have listed as "Orphan" any board mentioned in the "unknown / orphan"
sections of the original MAINTAINERS file.
If you look at the original MAINTAINERS, you'll see that some boards
were listed under a maintainer e-mail, and some boards were listed
under "unknown / orphan"; but not all boards were listed.
I set the board state in the new board.cfg to "Orphan" if and only
if the board was listed in such an "unknown / orphan" section, and to
"Active in any other case". This implies that:
- some boards were present in the old boards.cfg but not listed in
MAINTAINERS (e.g. sh7785lcr), which means there are "Active" boards
which do not have a maintainer;
- some "unknown / orphan" boards had a "last known maintainer address"
specified (e.g. EVB64260_750CX), which means there are "Orphan" boards
which have a maintainer listed.
IOW, a board's state (Active or Orphan) has no formal relationship with
this board having maintainers or not; the state only determines whether
this board should be built (Active) or not (Orphan).
Note that I have verified that ./MAKEALL -a arm built the same boards,
although I have not verified this for other architectures; and
that ./MAKEALL -m listed the same boards and maintainers (or more
exactly, listed the same boards and attributed the correct maintainers,
as some of the old ./MAKEALL -m output was incorrect), at meast for ARM
and PowerPC.
> Best Regards
> Masahiro Yamada
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-09-19 6:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 19:10 [U-Boot] [PATCH] Merge and reformat boards.cfg and MAINTAINERS Albert ARIBAUD
2013-09-11 13:52 ` [U-Boot] [PATCH v2] " Albert ARIBAUD
2013-09-12 15:11 ` Tom Rini
2013-09-17 0:55 ` Masahiro Yamada
2013-09-19 6:29 ` Albert ARIBAUD [this message]
2013-09-27 11:05 ` Masahiro Yamada
2013-10-03 21:32 ` Albert ARIBAUD
[not found] ` <7B43E01F5906F9448BF8BAACD5D26B3803CA11@DENBGAT9EH2MSX.ww902.siemens.net>
2013-09-15 5:36 ` Albert ARIBAUD
2013-09-16 6:55 ` Meier, Roger
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=20130919082949.1ea52c7f@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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