From: grant.likely@secretlab.ca (Grant Likely)
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: Thu, 9 May 2013 14:25:18 +0100 [thread overview]
Message-ID: <CACxGe6uo60OwRd7buPX4382_vE48MLWJYyB_ka+iS2FfVCa8mw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZtPhzLFicYYZF0SZfp4dMJars+Z-7hTUZQ1JjPExXW3A@mail.gmail.com>
On Mon, May 6, 2013 at 9:12 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On Mon, May 6, 2013 at 9:54 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>
>> 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.
>
> Point taken. I was in a discussion some time back with Greg and some
> other people and we concluded that unless the system mails you when
> something breaks it won't make a difference. And it mustn't flood you,
> just be very precise.
>
> Actually the autobuilder at kernel.org helped me out but then stopped
> building my trees at some point, but that was nice and the same thing
> doing boots would be great.
+1 on what has already been stated on this thread; An autobuilder does
work if it emails you when something breaks without spamming you. I've
also found the 0day build tester actually effective. It has caught
things that I've missed and I immediately was able to go an fix.
g.
next prev parent reply other threads:[~2013-05-09 13:25 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 [this message]
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
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=CACxGe6uo60OwRd7buPX4382_vE48MLWJYyB_ka+iS2FfVCa8mw@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--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;
as well as URLs for NNTP newsgroup(s).