From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Patch: numa.c broke in 2.4.6-pre8
Date: Sat, 30 Jun 2001 13:44:13 +0100 [thread overview]
Message-ID: <20010630134413.E12788@flint.arm.linux.org.uk> (raw)
Hi,
When building 2.4.6-pre8 with CONFIG_DISCONTIGMEM=y, I get the following
error:
numa.c:96: conflicting types for `_alloc_pages'
/usr/src/v2.4/linux-assabet/include/linux/mm.h:383: previous declaration of `_alloc_pages'
The following patch fixes this problem. Please apply.
--- orig/mm/numa.c Sat Jun 30 11:09:05 2001
+++ linux/mm/numa.c Sat Jun 30 13:40:37 2001
@@ -92,7 +92,7 @@
* This can be refined. Currently, tries to do round robin, instead
* should do concentratic circle search, starting from current node.
*/
-struct page * _alloc_pages(int gfp_mask, unsigned long order)
+struct page * _alloc_pages(unsigned int gfp_mask, unsigned long order)
{
struct page *ret = 0;
pg_data_t *start, *temp;
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
reply other threads:[~2001-06-30 12:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010630134413.E12788@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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