From: Alexander Beregalov <a.beregalov@gmail.com>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Akinobu Mita <akinobu.mita@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: next-0402: build fails at mm/debug-pagealloc.c
Date: Thu, 2 Apr 2009 15:21:25 +0400 [thread overview]
Message-ID: <a4423d670904020421k7395e11dwe70d4223cb817e0a@mail.gmail.com> (raw)
mm/debug-pagealloc.c: In function 'set_page_poison':
mm/debug-pagealloc.c:8: error: 'struct page' has no member named 'debug_flags'
mm/debug-pagealloc.c: In function 'clear_page_poison':
mm/debug-pagealloc.c:13: error: 'struct page' has no member named 'debug_flags'
mm/debug-pagealloc.c: In function 'page_poison':
mm/debug-pagealloc.c:18: error: 'struct page' has no member named 'debug_flags'
mm/debug-pagealloc.c: At top level:
mm/debug-pagealloc.c:120: error: redefinition of 'kernel_map_pages'
include/linux/mm.h:1278: error: previous definition of
'kernel_map_pages' was here
mm/debug-pagealloc.c: In function 'kernel_map_pages':
mm/debug-pagealloc.c:122: error: 'debug_pagealloc_enabled' undeclared
(first use in this function)
Should debug_flags really be in vm_area_struct instead of `struct page` ?
next reply other threads:[~2009-04-02 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 11:21 Alexander Beregalov [this message]
2009-04-02 16:31 ` [PATCH] build fix for generic debug pagealloc Akinobu Mita
2009-04-02 16:45 ` Andrew Morton
2009-04-03 16:44 ` Ingo Molnar
2009-04-03 20:38 ` Rafael J. Wysocki
2009-04-08 13:05 ` Ingo Molnar
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=a4423d670904020421k7395e11dwe70d4223cb817e0a@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).