public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: . debian
Date: Thu, 12 Aug 2004 23:30:55 +0000	[thread overview]
Message-ID: <200408121630.55814.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040810071417.GA5080@lst.de>

On Thursday, August 12, 2004 4:03 pm, dann frazier wrote:
> On Tue, Aug 10, 2004 at 09:14:17AM +0200, Christoph Hellwig wrote:
> > Btw, where is this patch from and why wasn't it discussed on linux-ia64?
>
> Alex Williamson sent it to me a few patches to fix build problems on
> an earlier 2.6 kernel - this is one that I still need when building
> UP kernels w/ 2.6.7.  Here's where the builds fail (both using the
> attached config).
>
> If I remove this patch, it forces DISCONTIGMEM on, which doesn't build w/o
> SMP:

I think you'll need CONFIG_NUMA and CONFIG_SMP for a generic kernel.

Jesse

  parent reply	other threads:[~2004-08-12 23:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  7:14 r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: . debian Christoph Hellwig
2004-08-10 15:51 ` Jesse Barnes
2004-08-12 23:03 ` dann frazier
2004-08-12 23:30 ` Jesse Barnes [this message]
2004-08-13  0:07 ` r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: Alex Williamson
2004-08-13  0:14 ` r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: . debian Jesse Barnes
2004-08-13  1:32 ` Jesse Barnes
2004-08-13  9:32 ` Christoph Hellwig
2004-08-13 15:29 ` Jesse Barnes
2004-08-13 16:02 ` r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: Alex Williamson
2004-08-13 16:16 ` r996 - in trunk/kernel/ia64/kernel-patch-2.6.7-ia64-2.6.7: . debian Jesse Barnes

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=200408121630.55814.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=linux-ia64@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