From: Jamie Lokier <jamie@shareable.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Eric Miao <eric.y.miao@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Paul Mundt <lethal@linux-sh.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: What's inside the pxa tree for this merge window
Date: Mon, 21 Sep 2009 21:32:28 +0100 [thread overview]
Message-ID: <20090921203228.GC14700@shareable.org> (raw)
In-Reply-To: <20090921200923.GF30821@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> Don't blame me for these delays - it's not my choice to impose such
> delays. I'd really like to fix those broken platforms right now. I
> just can't do so without causing additional delays for other issues.
> Blame Linus for imposing the "max one pull a week" rule on me.
Fwiw,I'm thinking the clrex-on-exception-return fix, at least, should
go to stable@kernel.org too if it's proving to be reliable, as it
affects userspace correctness on ARMv6+.
-- Jamie
next prev parent reply other threads:[~2009-09-21 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f17812d70909100446h17a1903fy74941945dbfc6943@mail.gmail.com>
[not found] ` <1253256227.4407.7.camel@pc-matejk>
[not found] ` <20090918074551.GA26058@n2100.arm.linux.org.uk>
2009-09-21 19:19 ` What's inside the pxa tree for this merge window Guennadi Liakhovetski
2009-09-21 20:09 ` Russell King - ARM Linux
2009-09-21 20:32 ` Jamie Lokier [this message]
2009-09-30 12:09 ` arm tree in broken state (was Re: What's inside the pxa tree for this merge window) Pavel Machek
2009-09-30 12:16 ` Guennadi Liakhovetski
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=20090921203228.GC14700@shareable.org \
--to=jamie@shareable.org \
--cc=eric.y.miao@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mchehab@infradead.org \
--cc=robert.jarzmik@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox