From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Andi Kleen <ak@muc.de>, Chuck Ebbert <76306.1226@compuserve.com>,
Zachary Amsden <zach@vmware.com>,
Jan Beulich <jbeulich@novell.com>,
linux-kernel@vger.kernel.org
Subject: Re: i386 pda patches
Date: Sun, 24 Sep 2006 22:38:27 -0700 [thread overview]
Message-ID: <45176B53.7040608@goop.org> (raw)
In-Reply-To: <20060924223427.6f42e77c.akpm@osdl.org>
Andrew Morton wrote:
> It may be related to the .config, rather than the CPU type.
>
Hm, wonder if it's !4K stacks...
J
next prev parent reply other threads:[~2006-09-25 5:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 8:35 i386 pda patches Andrew Morton
2006-09-25 0:40 ` Jeremy Fitzhardinge
2006-09-25 2:37 ` Randy Dunlap
2006-09-25 5:34 ` Andrew Morton
2006-09-25 5:37 ` QMC driver for MPC8272 Tang
2006-09-25 5:38 ` Jeremy Fitzhardinge [this message]
2006-09-25 6:05 ` i386 pda patches Andrew Morton
2006-09-25 6:29 ` Jeremy Fitzhardinge
2006-09-25 6:40 ` Andrew Morton
2006-09-25 18:52 ` Jeremy Fitzhardinge
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=45176B53.7040608@goop.org \
--to=jeremy@goop.org \
--cc=76306.1226@compuserve.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.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