From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [GIT pull] irq updates for 4.3
Date: Mon, 31 Aug 2015 09:47:37 -0700 [thread overview]
Message-ID: <55E48529.5070907@roeck-us.net> (raw)
In-Reply-To: <20150901021246.0ace2c6d@canb.auug.org.au>
On 08/31/2015 09:12 AM, Stephen Rothwell wrote:
> Hi Thomas,
>
> On Mon, 31 Aug 2015 12:04:37 +0200 (CEST) Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> Marc Zyngier (23):
>> irqchip/GIC: Convert to EOImode == 1
>
> This appears to lead to qemu arm boot tests silently failing (according
> to Guenter). This commit only appeared in next-20150831.
>
I think we really need more time between patches showing up in -next and
being pushed upstream. We have several new failures in -next which were
introduced after next-20150828, with this being the most serious one.
Of course, that additional time doesn't help if failures in -next are
known for weeks and still end up in mainline. Not really sure how
to solve that problem.
Guenter
next prev parent reply other threads:[~2015-08-31 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 10:04 [GIT pull] irq updates for 4.3 Thomas Gleixner
2015-08-31 16:12 ` Stephen Rothwell
2015-08-31 16:24 ` Marc Zyngier
2015-08-31 16:47 ` Guenter Roeck [this message]
2015-09-01 16:05 ` Thomas Gleixner
2015-09-01 16:10 ` [GIT pull V2] " Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2015-09-07 10:04 [GIT pull] " Thomas Gleixner
2015-09-18 11:58 Thomas Gleixner
2015-10-11 8:13 Thomas Gleixner
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=55E48529.5070907@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--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.