From: robherring2@gmail.com (Rob Herring)
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: Tue, 14 May 2013 15:39:00 -0500 [thread overview]
Message-ID: <5192A0E4.2070202@gmail.com> (raw)
In-Reply-To: <CAGNsrLDw0_yX9nkLYDg0e8-551P7r43UxziTp1TXyyxdiKR5nA@mail.gmail.com>
On 05/09/2013 12:51 PM, Fathi Boudra wrote:
> On 9 May 2013 19:13, Olof Johansson <olof@lixom.net> wrote:
>> On Thu, May 9, 2013 at 6:25 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
>>> 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
>> Yes, a builder is quite useful. Several of us do our own builds as well.
>>
>> When it comes to boot coverage, I'm not sure how successful a central
>> approach would be. It's something where I think Linaro could
>> contribute a lot for their member platforms, but I haven't seen much
>> engagement there yet.
>
> My previous post was lost. Sorry to repost..
>
> We've got a jenkins instance doing daily builds on various trees and
> boot testing on the few boards we've got in the lab:
> https://ci.linaro.org/jenkins/view/kernel-ci/
>
> But it hasn't attracted much interest so far... It's been here since a year.
Perhaps because there is no useful information there that I can find.
Where does it say what failed in the build? I see no artifacts or useful
console output.
It seems it was designed with Linaro's needs in mind and not kernel
maintainers' needs.
Rob
>
>> Beyond there, I'd say the expectation is that each maintainer should
>> keep an eye on their own platforms. They _should_ try building and
>> booting linux-next on their platforms, to catch regressions early. And
>> definitely around now, I'd like to see people boot mainline on their
>> platforms to make sure we haven't added any severe regressions in the
>> 3.10 merge window, etc. Some people are really good at this, others
>> less so.
>>
>> What's the old saying, you can lead a horse to water but you can't
>> make him drink? You can build a boot test cluster but you can't make
>> anyone pay attention to it. :(
>>
>> -Olof
>
> Cheers,
>
> Fathi
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2013-05-14 20:39 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 [this message]
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=5192A0E4.2070202@gmail.com \
--to=robherring2@gmail.com \
--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).