From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: Fwd: Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct"
Date: Mon, 06 May 2013 14:14:39 -0600 [thread overview]
Message-ID: <51880F2F.8010102@wwwdotorg.org> (raw)
In-Reply-To: <20130506195403.GJ18614@n2100.arm.linux.org.uk>
On 05/06/2013 01:54 PM, Russell King - ARM Linux wrote:
> On Mon, May 06, 2013 at 09:41:22PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 21:29 Mon 06 May , Linus Walleij wrote:
>>> On Sun, May 5, 2013 at 10:22 PM, Jean-Christophe PLAGNIOL-VILLARD
>>> <plagnioj@jcrosoft•com> wrote:
>>>
>>>> I was thinking to put a jenkins to test Linus HEAD all the time
>>>> And with some automatic test one some hw
>>>>
>>>> to detect it more quick
...
> My conclusion is that build and boot test systems just don't work in an
> open source environment as no one actively checks the results. Why would
> they - maintainers already have enough to do with reading 6500+ emails a
> month on mailing lists. Why bother going to look at a website as well
> which might give even more work.
Couldn't such a system email people pro-actively, so nobody had to do
any manual checking? The kisskb(?) build system does that, as does the
"zero day build system" thing from Intel, and I find them quite useful.
Personally, I do the build/test checks manually myself, so if an
automated system were to do it, it'd save me work rather than give me
more work.
next prev parent reply other threads:[~2013-05-06 20:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAK5ve-KXdS8az=Gtja-mF=Z3_EeZVA7bLYSU0EE2mf5bHmSUKw@mail.gmail.com>
[not found] ` <CAK5ve-KBDyvjNRVMcXgfnhYcajdcGsuAKaepzCBt+epiXoYvSw@mail.gmail.com>
2013-04-29 19:59 ` Fwd: Tegra 30 System hangs because of commit "pinctrl: move subsystem mutex to pinctrl_dev struct" Stephen Warren
2013-04-29 20:54 ` Bryan Wu
2013-05-03 14:22 ` Linus Walleij
2013-05-04 13:30 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-04 20:52 ` Linus Walleij
2013-05-05 11:28 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-05 19:57 ` Linus Walleij
2013-05-05 20:22 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 19:29 ` Linus Walleij
2013-05-06 19:32 ` Bryan Wu
2013-05-06 19:41 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 19:54 ` Russell King - ARM Linux
2013-05-06 20:12 ` Linus Walleij
2013-05-09 13:25 ` Grant Likely
2013-05-09 16:13 ` Olof Johansson
2013-05-09 17:51 ` Fathi Boudra
2013-05-10 9:29 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-14 20:39 ` Rob Herring
2013-05-15 14:13 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 20:14 ` Stephen Warren [this message]
2013-05-06 20:19 ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-06 20:40 ` Bryan Wu
2013-05-06 20:25 ` Jean-Christophe PLAGNIOL-VILLARD
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=51880F2F.8010102@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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