diff options
| author | Russell King <rmk@dyn-67.arm.linux.org.uk> | 2008-11-06 17:11:07 +0000 |
|---|---|---|
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2008-11-06 17:13:47 +0000 |
| commit | ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6 (patch) | |
| tree | 7532eb50e674402f8f658094acb71b8dfb1117bf /mm/allocpercpu.c | |
| parent | d2ed5cb80a241518dd71f467c884bfabbe15f68c (diff) | |
| download | op-kernel-dev-ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6.zip op-kernel-dev-ab4f2ee130d5ffcf35616e1f5c6ab75af5b463b6.tar.gz | |
[ARM] fix naming of MODULE_START / MODULE_END
As of 73bdf0a60e607f4b8ecc5aec597105976565a84f, the kernel needs
to know where modules are located in the virtual address space.
On ARM, we located this region between MODULE_START and MODULE_END.
Unfortunately, everyone else calls it MODULES_VADDR and MODULES_END.
Update ARM to use the same naming, so is_vmalloc_or_module_addr()
can work properly. Also update the comment on mm/vmalloc.c to
reflect that ARM also places modules in a separate region from the
vmalloc space.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'mm/allocpercpu.c')
0 files changed, 0 insertions, 0 deletions
