diff options
| author | Lennert Buytenhek <buytenh@wantstofly.org> | 2006-09-18 18:26:25 -0400 |
|---|---|---|
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2006-09-25 05:25:53 -0400 |
| commit | c852ac80440db9b0a47f48578e9c6303078abbc1 (patch) | |
| tree | 0c7fc1ca7700b0196a20242ca306003db7e35fb6 /include/asm-arm/arch-iop33x/vmalloc.h | |
| parent | 475549faa161f4e002225f2ef75fdd2a6d83d151 (diff) | |
[ARM] 3832/1: iop3xx: coding style cleanup
Since the iop32x code isn't iop321-specific, and the iop33x code isn't
iop331-specfic, do a s/iop321/iop32x/ and s/iop331/iop33x/, and tidy up
the code to conform to the coding style guidelines somewhat better.
Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'include/asm-arm/arch-iop33x/vmalloc.h')
| -rw-r--r-- | include/asm-arm/arch-iop33x/vmalloc.h | 15 |
1 files changed, 2 insertions, 13 deletions
diff --git a/include/asm-arm/arch-iop33x/vmalloc.h b/include/asm-arm/arch-iop33x/vmalloc.h index b5092027449e..66f545a7f4fc 100644 --- a/include/asm-arm/arch-iop33x/vmalloc.h +++ b/include/asm-arm/arch-iop33x/vmalloc.h | |||
| @@ -1,16 +1,5 @@ | |||
| 1 | /* | 1 | /* |
| 2 | * linux/include/asm-arm/arch-iop33x/vmalloc.h | 2 | * include/asm-arm/arch-iop33x/vmalloc.h |
| 3 | */ | 3 | */ |
| 4 | 4 | ||
| 5 | /* | 5 | #define VMALLOC_END 0xfe000000 |
| 6 | * Just any arbitrary offset to the start of the vmalloc VM area: the | ||
| 7 | * current 8MB value just means that there will be a 8MB "hole" after the | ||
| 8 | * physical memory until the kernel virtual memory starts. That means that | ||
| 9 | * any out-of-bounds memory accesses will hopefully be caught. | ||
| 10 | * The vmalloc() routines leaves a hole of 4kB between each vmalloced | ||
| 11 | * area for the same reason. ;) | ||
| 12 | */ | ||
| 13 | //#define VMALLOC_END (0xe8000000) | ||
| 14 | /* increase usable physical RAM to ~992M per RMK */ | ||
| 15 | #define VMALLOC_END (0xfe000000) | ||
| 16 | |||