[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0801261720310.15243@fbirervta.pbzchgretzou.qr>
Date: Sat, 26 Jan 2008 17:27:48 +0100 (CET)
From: Jan Engelhardt <jengelh@...putergmbh.de>
To: monstr@...str.eu
cc: linux-kernel@...r.kernel.org, stephen.neuendorffer@...inx.com,
john.williams@...alogix.com, microblaze-uclinux@...e.uq.edu.au
Subject: Re: [PATCH 11/52] [microblaze] kernel modules support
On Jan 24 2008 16:02, monstr@...str.eu wrote:
>+
>+/* module handling */
>+EXPORT_SYMBOL(PAGE_OFFSET);
This looks really ugly. PAGE_OFFSET is usually a macro.
I looked in patch 29/52 where PAGE_OFFSET is defined (unsigned int
PAGE_OFFSET), which got me wondered: PAGE_OFFSET can be a runtime
variable when it is a constant on most other arches?
That being said, I'd use
#define PAGE_OFFSET __page_offset
in some header file and in the .c file:
unsigned int __page_offset;
EXPORT_SYMBOL(__page_offset);
that is how arch-frv and -uml seem to do it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists