From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mundt Subject: Re: [PATCH 02/20] mm: generic show_mem() Date: Sat, 28 Jun 2008 13:22:40 +0900 Message-ID: <20080628042240.GB25492@linux-sh.org> References: <20080627115349.743368154@saeurebad.de> <20080627120048.059732179@saeurebad.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mta23.gyao.ne.jp ([125.63.38.249]:45312 "EHLO mx.gate01.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751430AbYF1EZS (ORCPT ); Sat, 28 Jun 2008 00:25:18 -0400 Content-Disposition: inline In-Reply-To: <20080627120048.059732179@saeurebad.de> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Johannes Weiner Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org On Fri, Jun 27, 2008 at 01:53:51PM +0200, Johannes Weiner wrote: > This implements a platform-independent version of show_mem(). > > Signed-off-by: Johannes Weiner Looking at this again, does having this as a Kconfig option really make sense? We have no tristate in-tree users of this that I can see, wouldn't this be better off in lib/? It would be preferable not to let the HAVE_foo stuff get out of hand if we can avoid it.