public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: vince@kyllikki.org (Vincent Sanders)
To: linux-arm-kernel@lists.infradead.org
Subject: Error for machine_is_m28evk
Date: Tue, 8 Nov 2011 14:53:23 +0000	[thread overview]
Message-ID: <20111108145322.GE856@kyllikki.org> (raw)
In-Reply-To: <20111108140557.GC10538@mudshark.cambridge.arm.com>

On Tue, Nov 08, 2011 at 02:05:58PM +0000, Will Deacon wrote:
> On Tue, Nov 08, 2011 at 01:37:44PM +0000, Russell King - ARM Linux wrote:
> > (b) with the loss of facilities like kautobuild (no one noticed for six
> >     months that simtec had shut it down...), we have lost any kind of
> >     automated detection for these kinds of issues.
> 
> Have Simtec /actually/ shut this down, or did it just die when kernel.org
> was hacked and nobody has poked it since then?
> 
> The website is still up and doesn't seem to mention its demise:
> 
> http://armlinux.simtec.co.uk/kautobuild/
> 
> Will

Simtec never really owned this it was more they sponsored the server
space and my time to run it. My employer have been very good and were
willing to keep paying for it but in the end it was my decision to
shut it down.

I posted the five year review some time ago and except for several
fairly abusive mails including that I should stop upsetting developers
by showing when things failed and several more *demands* that I
implemented additional features I received no feedback. With the
notable exception of Russell who was supportive.

As there were a grand total of four people subscribed to the results
list and the number of pageviews per month was under the hundred mark
I simply stopped the cron jobs in May and turned it off. I figured if
anyone really cared they would shout.

No one noticed until Russell mentioned it on IRC the other day so I am
fairly sure that me compiling 200+ default configs two or three times
a day was completely pointless as no one was looking at the
results. Even the yearly reports I wrote seemed to upset more people
than they helped.

My point of view is that the ARM "community" and the majority of
maintainers only care about the SoC and board they are working on
right that moment and once it is in mainline (well for a long time
that read "once the patches were posted to the mailing list") it can be
abandoned to Russell and janitors like myself. 

There were of course always exceptions to the rule and I know there is
great effort to improve the situation now. However it seems to me that
kautobuild providing build coverage was simply not useful in those
efforts. 

I continue to provide list moderation and work in other areas of ARM
Linux but I do not think my time was best spent maintaining (at not
inconsiderable personal expense) the kautobuilder system,

-- 
Regards Vincent
http://www.kyllikki.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111108/6b012f38/attachment.sig>

  parent reply	other threads:[~2011-11-08 14:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  1:49 Error for machine_is_m28evk Fabio Estevam
2011-11-08  5:16 ` Shawn Guo
2011-11-08  6:30 ` Stefano Babic
2011-11-08  7:53   ` Uwe Kleine-König
2011-11-08  8:09     ` Jason Liu
2011-11-08  8:53       ` Russell King - ARM Linux
2011-11-08 12:53         ` Shawn Guo
2011-11-08 13:37           ` Russell King - ARM Linux
2011-11-08 14:05             ` Will Deacon
2011-11-08 14:36               ` Arnaud Patard (Rtp)
2011-11-08 14:45               ` Russell King - ARM Linux
2011-11-08 14:53               ` Vincent Sanders [this message]
2011-11-16  5:59           ` Shawn Guo
2011-11-16  8:42             ` Russell King - ARM Linux
2011-11-16 13:58               ` Shawn Guo
2011-11-16 18:48                 ` Uwe Kleine-König
2011-11-16 22:28                   ` Shawn Guo

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=20111108145322.GE856@kyllikki.org \
    --to=vince@kyllikki.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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