[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871w5nouwp.fsf@saeurebad.de>
Date: Thu, 03 Apr 2008 16:49:42 +0200
From: Johannes Weiner <hannes@...urebad.de>
To: Sam Ravnborg <sam@...nborg.org>
Cc: Heiko Carstens <heiko.carstens@...ibm.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, mingo@...e.hu,
davem@...emloft.net, hskinnemoen@...el.com, cooloney@...nel.org,
starvik@...s.com, dhowells@...hat.com, ysato@...rs.sf.net,
takata@...ux-m32r.org, geert@...ux-m68k.org, ralf@...ux-mips.org,
kyle@...isc-linux.org, paulus@...ba.org, schwidefsky@...ibm.com,
lethal@...ux-sh.org, jdike@...toit.com, miles@....org,
chris@...kel.net, rmk@....linux.org.uk, tony.luck@...el.com
Subject: Re: [RFC 01/22] Generic show_mem() implementation
Hi,
Sam Ravnborg <sam@...nborg.org> writes:
>> e.g. we currently have this in arch/s390/Kconfig:
>>
>> config S390
>> def_bool y
>> select HAVE_OPROFILE
>> select HAVE_KPROBES
>> select HAVE_KRETPROBES
>>
>> just add a select HAVE_GENERIC_SHOWMEM or something like that in the arch
>> specific patches.
> Seconded.
> See Documentation/kbuild/kconfig-language.txt for a few more hints
> how to do it.
After more thinking about it, wouldn't it be better to have
HAVE_ARCH_SHOW_MEM in mm/Kconfig and let archs with their own show_mem()
select it? Because there are far more archs that use the generic
version than those having their own.
Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists