| commit | 0eefed84fe9e1eb90f4b089ead95904306b23233 | |
| author | Geert Uytterhoeven <geert@linux-m68k.org> | |
| Sun, 31 Oct 2010 20:23:55 +0000 (31 21:23 +0100) | ||
| committer | Geert Uytterhoeven <geert@linux-m68k.org> | |
| Wed, 5 Jan 2011 20:17:19 +0000 (5 21:17 +0100) | ||
| tree | e937ef45698cb39d8986bdef335cf4ee7233a8c5 | treesnapshot (tar.gz zip) |
| parent | 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5 | commitdiff |
m68k/sun3: Kill pte_unmap() warnings
Since commit 31c911329e048b715a1dfeaaf617be9430fd7f4e ("mm: check the argument
of kunmap on architectures without highmem"), we get lots of warnings like
arch/m68k/kernel/sys_m68k.c:508: warning: passing argument 1 of ‘kunmap’ from incompatible pointer type
As m68k doesn't support highmem anyway, open code the calls to kmap() and
kunmap() (the latter is a no-op) to kill the warnings, like is done on most
other architectures without CONFIG_HIGHPTE.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sam Creasey <sammy@sammy.net>
Since commit 31c911329e048b715a1dfeaaf617be9430fd7f4e ("mm: check the argument
of kunmap on architectures without highmem"), we get lots of warnings like
arch/m68k/kernel/sys_m68k.c:508: warning: passing argument 1 of ‘kunmap’ from incompatible pointer type
As m68k doesn't support highmem anyway, open code the calls to kmap() and
kunmap() (the latter is a no-op) to kill the warnings, like is done on most
other architectures without CONFIG_HIGHPTE.
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sam Creasey <sammy@sammy.net>
| arch/m68k/include/asm/sun3_pgtable.h | diffblobblamehistory |