From: Andi Kleen <ak@suse.de>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: vgoyal@in.ibm.com, "Eric W. Biederman" <ebiederm@xmission.com>,
akpm@osdl.org, James.Bottomley@steeleye.com,
linux-kernel@vger.kernel.org, fastboot@lists.osdl.org
Subject: Re: [PATCH 0/4] stack overflow safe kdump (2.6.18-rc1-i386) try#2
Date: Tue, 11 Jul 2006 08:59:17 +0200 [thread overview]
Message-ID: <200607110859.17454.ak@suse.de> (raw)
In-Reply-To: <1152597884.2414.53.camel@localhost.localdomain>
On Tuesday 11 July 2006 08:04, Fernando Luis Vázquez Cao wrote:
> Hi,
>
> I tried to incorporate all the ideas received after the previous post
> (thank you!). In particular I hope the new code is handling the Voyager
> case properly.
Looks all reasonable to me.
-Andi
next prev parent reply other threads:[~2006-07-11 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 6:04 [PATCH 0/4] stack overflow safe kdump (2.6.18-rc1-i386) try#2 Fernando Luis Vázquez Cao
2006-07-11 6:59 ` Andi Kleen [this message]
2006-07-11 7:13 ` Eric W. Biederman
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=200607110859.17454.ak@suse.de \
--to=ak@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=fernando@oss.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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