From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: GENERIC build failure
Date: Fri, 13 Feb 2004 22:48:42 +0000 [thread overview]
Message-ID: <20040213144842.3164a5bc.akpm@osdl.org> (raw)
In-Reply-To: <200402132133.i1DLXaYS026393@napali.hpl.hp.com>
I dropped the patch because it's fixed in Len's tree.
If someone can send me a tested standalone patch then sure.
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> Andrew,
>
> Could you push this fix into Linus' tree? I'd consider it urgent,
> because we do want GENERIC configs to build out-of-the-box for 2.6.3.
>
> Thanks,
>
> --david
>
> >>>>> On Fri, 13 Feb 2004 13:51:05 -0800, jbarnes@sgi.com (Jesse Barnes) said:
>
> Jesse> This is fixed in Andrew's tree. I'm not sure why Len hasn't
> Jesse> pushed it to Linus yet though.
>
> Jesse> The fix is a simple change of NR_MEMBLKS to NR_NODE_MEMBLKS.
>
> Jesse> Jesse
>
> Jesse> On Fri, Feb 13, 2004 at 01:33:36PM -0800, David Mosberger
> Jesse> wrote:
> >> According to this page:
> >>
> >> http://www.gelato.unsw.edu.au/kerncomp/
> >>
> >> Generic kernel builds are still failing, due to some NUMA cruft.
> >> I thought this was supposed to be fixed already. Can someone who
> >> cares about NUMA investigate?
> >>
> >> -d-avid
> >> -
> >> To unsubscribe from this list: send the line "unsubscribe
> >> linux-ia64" in the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-02-13 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 21:33 GENERIC build failure David Mosberger
2004-02-13 21:51 ` Jesse Barnes
2004-02-13 21:55 ` David Mosberger
2004-02-13 22:48 ` Andrew Morton [this message]
2004-02-13 22:55 ` 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=20040213144842.3164a5bc.akpm@osdl.org \
--to=akpm@osdl.org \
--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