From: Guenter Roeck <linux@roeck-us.net>
To: Davidlohr Bueso <davidlohr@hp.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Aswin Chandramouleeswaran <aswin@hp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arch,locking: Ciao arch_mutex_cpu_relax()
Date: Fri, 08 Aug 2014 03:45:09 -0700 [thread overview]
Message-ID: <53E4AA35.1060703@roeck-us.net> (raw)
In-Reply-To: <1407460714.2513.19.camel@buesod1.americas.hpqcorp.net>
On 08/07/2014 06:18 PM, Davidlohr Bueso wrote:
> On Tue, 2014-08-05 at 10:42 -0700, Davidlohr Bueso wrote:
>> On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
>>> It looks like you forgot to update frv? It's been failing on -next since a
>>> few days:
>
> Anyway developers can be alerted sooner about this (ie: while its still
> in -next phase), like automated emails or something? This would be extra
> nice for those archs that are harder to get tested.
>
Not sure if that would help. After all, images are being built.
People just don't care enough to have a look.
FWIW, next-20140808 build results on my build/test farm:
total: 132 pass: 120 fail: 12
Failed builds:
frv:defconfig
mips:nlm_xlp_defconfig
openrisc:defconfig
powerpc:allmodconfig (binutils 2.23 and 2.24)
powerpc:mpc83xx_defconfig (ditto)
powerpc:mpc85xx_defconfig (ditto)
powerpc:mpc85xx_smp_defconfig (ditto)
unicore32:defconfig
with qemu test runs failing for arm, mips, mips64, and ppc.
Which points to the next problem: I simply do not have the time to track down
all those failures, and I would guess neither do others who might be interested.
Geert is doing an excellent job trying to report and fix things, but quite frankly
sometimes one feels like Sisyphus trying to keep builds clean.
Guenter
next prev parent reply other threads:[~2014-08-08 10:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 18:21 [PATCH] arch,locking: Ciao arch_mutex_cpu_relax() Davidlohr Bueso
2014-06-23 6:54 ` Peter Zijlstra
2014-06-23 7:13 ` Vineet Gupta
2014-06-23 11:34 ` Peter Zijlstra
2014-06-23 6:58 ` Peter Zijlstra
2014-06-24 15:06 ` Davidlohr Bueso
2014-06-25 6:25 ` Heiko Carstens
2014-06-25 11:57 ` Linus Torvalds
2014-06-29 22:09 ` [PATCH v2] " Davidlohr Bueso
2014-08-05 13:04 ` Geert Uytterhoeven
2014-08-05 17:42 ` Davidlohr Bueso
2014-08-08 1:18 ` Davidlohr Bueso
2014-08-08 10:45 ` Guenter Roeck [this message]
2014-08-15 19:34 ` Guenter Roeck
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=53E4AA35.1060703@roeck-us.net \
--to=linux@roeck-us.net \
--cc=aswin@hp.com \
--cc=davidlohr@hp.com \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.