From: NIIBE Y. <gn...@m1...> - 2001-08-10 14:03:30
|
2001-08-10 NIIBE Yutaka <gn...@m1...> * arch/sh/mm/cache-sh4.c (__flush_wback_region, __flush_purge_region): Comment fix for the arguments. * arch/sh/mm/cache-sh3.c (__flush_wback_region, __flush_purge_region): Likewise. Index: arch/sh/mm/cache-sh3.c =================================================================== RCS file: /cvsroot/linuxsh/kernel/arch/sh/mm/cache-sh3.c,v retrieving revision 1.3 diff -u -r1.3 cache-sh3.c --- arch/sh/mm/cache-sh3.c 2001/08/10 13:58:55 1.3 +++ arch/sh/mm/cache-sh3.c 2001/08/10 14:01:05 @@ -148,7 +148,8 @@ * Is this really worth it, or should we just alias this routine * to __flush_purge_region too? * - * START, END: Virtual Address (U0, P1, or P3) + * START: Virtual Address (U0, P1, or P3) + * SIZE: Size of the region. */ void __flush_wback_region(void *start, int size) @@ -180,7 +181,8 @@ /* * Write back the dirty D-caches and invalidate them. * - * START, END: Virtual Address (U0, P1, or P3) + * START: Virtual Address (U0, P1, or P3) + * SIZE: Size of the region. */ void __flush_purge_region(void *start, int size) { Index: arch/sh/mm/cache-sh4.c =================================================================== RCS file: /cvsroot/linuxsh/kernel/arch/sh/mm/cache-sh4.c,v retrieving revision 1.14 diff -u -r1.14 cache-sh4.c --- arch/sh/mm/cache-sh4.c 2001/08/09 00:27:04 1.14 +++ arch/sh/mm/cache-sh4.c 2001/08/10 14:01:05 @@ -107,7 +107,8 @@ /* * Write back the dirty D-caches, but not invalidate them. * - * START, END: Virtual Address (U0, P1, or P3) + * START: Virtual Address (U0, P1, or P3) + * SIZE: Size of the region. */ void __flush_wback_region(void *start, int size) { @@ -127,7 +128,8 @@ /* * Write back the dirty D-caches and invalidate them. * - * START, END: Virtual Address (U0, P1, or P3) + * START: Virtual Address (U0, P1, or P3) + * SIZE: Size of the region. */ void __flush_purge_region(void *start, int size) { -- |