From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andrew Morton <akpm@osdl.org>,
mbligh@google.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc1-git4 and 2.6.18-rc1-mm1 OOM's on boot
Date: Fri, 14 Jul 2006 20:13:20 +1000 [thread overview]
Message-ID: <1152872000.23037.53.camel@localhost.localdomain> (raw)
In-Reply-To: <44B756AB.50102@shadowen.org>
> I can only see two outstanding issues. An IDE lost interrupt issue on a
> blade we have under test which I believe benh is looking at, and what
> looks like an s390 tool chain issue which I am told is being looked at.
Yeah, well, I'm trying to look at it... between flights :)
Ben.
prev parent reply other threads:[~2006-07-14 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 16:53 2.6.18-rc1-git4 and 2.6.18-rc1-mm1 OOM's on boot Martin Bligh
2006-07-13 1:16 ` Andrew Morton
2006-07-13 1:24 ` Martin Bligh
2006-07-13 14:12 ` Andy Whitcroft
2006-07-14 8:00 ` Andy Whitcroft
2006-07-14 8:08 ` Andrew Morton
2006-07-14 8:32 ` Andy Whitcroft
2006-07-14 10:13 ` Benjamin Herrenschmidt [this message]
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=1152872000.23037.53.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
/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