All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Merge and reformat boards.cfg and MAINTAINERS
Date: Fri, 27 Sep 2013 20:05:35 +0900	[thread overview]
Message-ID: <20130927200535.15F6.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <20130919082949.1ea52c7f@lilith>

Hello Albert

> 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.

To sum up things, boards have actually 3 states:

 (1) Active:
        had a maintainer in the original MAINTAINERS file

 (2) Orphan:
        listed under unknown/orphan in the original MAINTAINERS file

 (3) maybe Active, maybe Orphan:
        not mentioned in the original MAINTAINERS file

You pushed both (1) and (3) into Active state in the new boards.cfg
although many boards in (3) might not have a maintainer.

In such a case, what is the meaning to categorize into Active or Orphan?


> 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).

I think unknown/orphan stands for "no maintainers" in the original MAINTAINERS file.
Now you recongnize this as "Should not be built".
Is this the same meaning?

In my opinion, 'Orphan' might be a misleading term for the latter.
Active / Dead ?


How abount reconsidering a bit more about this categorization?


Best Regards
Masahiro Yamada

  reply	other threads:[~2013-09-27 11:05 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
2013-09-27 11:05         ` Masahiro Yamada [this message]
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=20130927200535.15F6.AA925319@jp.panasonic.com \
    --to=yamada.m@jp.panasonic.com \
    --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 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.