From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: GENERIC build failure
Date: Fri, 13 Feb 2004 22:55:52 +0000 [thread overview]
Message-ID: <20040213225551.GA23760@sgi.com> (raw)
In-Reply-To: <200402132133.i1DLXaYS026393@napali.hpl.hp.com>
On Fri, Feb 13, 2004 at 02:48:42PM -0800, Andrew Morton wrote:
>
> I dropped the patch because it's fixed in Len's tree.
>
> If someone can send me a tested standalone patch then sure.
Here you go.
Jesse
=== drivers/acpi/numa.c 1.7 vs edited ==--- 1.7/drivers/acpi/numa.c Tue Jan 13 01:52:03 2004
+++ edited/drivers/acpi/numa.c Wed Feb 11 17:31:34 2004
@@ -172,7 +172,7 @@
NR_CPUS);
result = acpi_table_parse_srat(ACPI_SRAT_MEMORY_AFFINITY,
acpi_parse_memory_affinity,
- NR_MEMBLKS);
+ NR_NODE_MEMBLKS);
} else {
/* FIXME */
printk("Warning: acpi_table_parse(ACPI_SRAT) returned %d!\n",result);
prev parent reply other threads:[~2004-02-13 22:55 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
2004-02-13 22:55 ` Jesse Barnes [this message]
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=20040213225551.GA23760@sgi.com \
--to=jbarnes@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