public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] livetime of boards
Date: Thu, 07 Nov 2013 13:50:07 +0100	[thread overview]
Message-ID: <527B8C7F.6060503@denx.de> (raw)
In-Reply-To: <20131107121241.C93953811DF@gemini.denx.de>

Hello Wolfgang,

Am 07.11.2013 13:12, schrieb Wolfgang Denk:
> Dear Heiko,
>
> In message<527B7EE6.4030307@denx.de>  you wrote:
>>
>> Hmm... I hope we get a lot of such EMails ... and think, this is not
>> a big problem ... Or, maybe, if we get a lot of such EMails, maybe we
>> open a u-boot-testing list?
>
> NAK.  Mailing lists are good for some kind of information - especially
> for such information that is read by humans.
>
> All you want to do here is feed a database with data.  This is not
> what mailing lists were made for, so we should really use a more
> appropriate interface.

Ok. But this status report can be in readable text format ;-)

>> See my proposal for the livetime counter:
>>
>> livetime init value n (n=4)
>> livetimer decrement on every new release
>> livetimer set to n, if in release cycle comes a test report
>> livetimer == 0 ->  EMail to board maintainer, board reached end of live in
>>                     mainline, please send test report.
>> livetimer == -1 ->  board get deleted
>
> This is too simple in one respect (as you are not including
> information that may be vital, like which exact commit ID has been
> tested, or which tool chain has been used to build it).

Ok.

> Also we should probably not only allow for positive test reports, but
> also allow to report failures (to mark board support as broken).

Yep, this will set livetime = 0 -> EMail to board maintainer ...

> All this cannot be done in  boards.cfg .
>
> And there is no need to as long as we provide tools to query for any
> information we might be interested in.

Ok, then we must define this way ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  reply	other threads:[~2013-11-07 12:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 13:05 [U-Boot] livetime of boards Heiko Schocher
2013-11-05 20:37 ` Tom Rini
2013-11-06  7:50   ` Wolfgang Denk
2013-11-07  8:17     ` Heiko Schocher
2013-11-07  9:37       ` Andreas Bießmann
2013-11-07 10:39         ` Heiko Schocher
2013-11-07 11:13           ` Albert ARIBAUD
2013-11-07 11:42             ` Heiko Schocher
2013-11-07 12:06               ` Wolfgang Denk
2013-11-07 12:21                 ` Heiko Schocher
2013-11-07 11:24           ` Andreas Bießmann
2013-11-07 11:52             ` Heiko Schocher
2013-11-07 12:12               ` Wolfgang Denk
2013-11-07 12:50                 ` Heiko Schocher [this message]
2013-11-07 19:19                   ` Wolfgang Denk
2013-11-08  5:31                     ` Heiko Schocher
2013-11-08  7:19                       ` Wolfgang Denk
2013-11-07 12:01             ` Wolfgang Denk
2013-11-07 12:16               ` Andreas Bießmann
2013-11-07 12:46               ` Heiko Schocher
2013-11-07 19:15                 ` Wolfgang Denk
2013-11-08  5:28                   ` Heiko Schocher
2013-11-08  6:20                     ` Wolfgang Denk
2013-11-08  7:11                       ` Heiko Schocher
2013-11-07 13:31         ` Tom Rini
2013-11-07 14:27           ` Andreas Bießmann
2013-11-07 19:26           ` Wolfgang Denk
2013-11-07 20:51             ` Tom Rini
2013-11-07 21:06               ` Wolfgang Denk
2013-11-08  5:35             ` Heiko Schocher
2013-11-08  4:58           ` Heiko Schocher

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=527B8C7F.6060503@denx.de \
    --to=hs@denx.de \
    --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