kernel-fxtec-pro1x/arch/ppc64
Mike Kravetz 0286486783 [PATCH] Memory Add Fixes for ppc64
On Tue, Nov 08, 2005 at 08:12:56AM +1100, Benjamin Herrenschmidt wrote:
> Yes, the MAX_ORDER should be different indeed. But can Kconfig do that ?
> That is have the default value be different based on a Kconfig option ?
> I don't see that ... We may have to do things differently here...

This seems to be done in other parts of the Kconfig file.  Using those
as an example, this should keep the MAX_ORDER block size at 16MB.

Signed-off-by: Mike Kravetz <kravetz@us.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2005-11-08 11:20:00 +11:00
..
boot [PATCH] ppc64: Fix zImage boot 2005-11-07 07:53:23 -08:00
configs [PATCH] ppc64: update defconfigs 2005-10-19 23:12:36 -07:00
kernel [PATCH] ppc64: More U3 device-tree fixes 2005-11-08 11:17:53 +11:00
xmon powerpc: Merge xmon 2005-10-28 22:53:37 +10:00
defconfig [PATCH] ppc64: compile nls_cp437 and nls_iso8859_1 into the kernel in defconfig 2005-10-29 15:14:44 +10:00
Kconfig [PATCH] Memory Add Fixes for ppc64 2005-11-08 11:20:00 +11:00
Kconfig.debug [PATCH] powerpc: Kill ppcdebug 2005-11-07 12:37:45 +11:00
Makefile powerpc: fix __strnlen_user in merge tree 2005-11-01 14:34:17 +11:00