From: Andi Kleen <andi@firstfloor.org>
To: Joerg Friedrich <Joerg.Friedrich@friedrich-kn.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-gitX and pmd_bad() on x86_32
Date: Fri, 25 Apr 2008 11:48:02 +0200 [thread overview]
Message-ID: <8763u6xo31.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080425084007.GC14387@stardust.frews.de> (Joerg Friedrich's message of "Fri, 25 Apr 2008 10:40:07 +0200")
Joerg Friedrich <Joerg.Friedrich@friedrich-kn.de> writes:
> Yesterday I tried to compile 2.6.25-git5 but I ran into a "Unknown
> Symbol" (pmd_bad) warning from linker while compiling the nvidia-binary module.
pmd_bad is always optional. You can safely make it return 0 in some local
macro.
> AFAICS, x86_32 is the only architecture where pmd_bad is neither a
> define or a static inline. Including asm/pgtable.h is no longer
> sufficient on x868_32. Is this behaviour intended or is there just a
> EXPORT_SYMBOL missing?
Kernel changes generally don't care about out of tree modules.
Also pmd_bad() is kind of internal anyways.
-Andi
prev parent reply other threads:[~2008-04-25 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 8:40 2.6.25-gitX and pmd_bad() on x86_32 Joerg Friedrich
2008-04-25 9:48 ` Andi Kleen [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=8763u6xo31.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Joerg.Friedrich@friedrich-kn.de \
--cc=linux-kernel@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