public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
Cc: akpm@osdl.org, James.Bottomley@steeleye.com,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	fastboot@lists.osdl.org, ak@suse.de,
	linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] [PATCH 1/3] stack overflow safe kdump (2.6.18-rc1-i386) - safe_smp_processor_id
Date: Tue, 11 Jul 2006 16:25:15 +1000	[thread overview]
Message-ID: <12668.1152599115@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 11 Jul 2006 15:15:14 +0900." <1152598514.2414.66.camel@localhost.localdomain>

Fernando Luis =?ISO-8859-1?Q?V=E1zquez?= Cao (on Tue, 11 Jul 2006 15:15:14 +0900) wrote:
>I prepared new patches and hopefully I got it right this time, Do they
>look good this time (PATCH 4/4 in particular)?

Looks good.


  reply	other threads:[~2006-07-11  6:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  7:50 [PATCH 1/3] stack overflow safe kdump (2.6.18-rc1-i386) - safe_smp_processor_id Fernando Luis Vázquez Cao
2006-07-10  8:27 ` [Fastboot] " Keith Owens
2006-07-10 10:15   ` Fernando Luis Vázquez Cao
2006-07-10 11:37     ` Eric W. Biederman
2006-07-11  4:21       ` Fernando Luis Vázquez Cao
2006-07-11  4:44         ` Fernando Luis Vázquez Cao
2006-07-11  4:55         ` Keith Owens
2006-07-11  6:15           ` Fernando Luis Vázquez Cao
2006-07-11  6:25             ` Keith Owens [this message]
2006-07-10 12:04     ` Keith Owens
2006-07-11  6:40       ` Fernando Luis Vázquez Cao
2006-07-10 14:16 ` James Bottomley
2006-07-10 18:20   ` Eric W. Biederman
2006-07-10 20:58     ` James Bottomley
2006-07-11  3:42       ` Eric W. Biederman
2006-07-11 12:36         ` James Bottomley
2006-07-11 19:41           ` Eric W. Biederman
2006-07-11  6:21       ` [Fastboot] " Fernando Luis Vázquez Cao

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=12668.1152599115@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=James.Bottomley@steeleye.com \
    --cc=ak@suse.de \
    --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 \
    /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