From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261302AbVCZVip (ORCPT ); Sat, 26 Mar 2005 16:38:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261303AbVCZVio (ORCPT ); Sat, 26 Mar 2005 16:38:44 -0500 Received: from fire.osdl.org ([65.172.181.4]:23685 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261302AbVCZViU (ORCPT ); Sat, 26 Mar 2005 16:38:20 -0500 Message-ID: <4245D63A.8060204@osdl.org> Date: Sat, 26 Mar 2005 13:38:02 -0800 From: "Randy.Dunlap" User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dave Hansen CC: Linux Kernel Mailing List , linux-mm , Andy Whitcroft Subject: Re: [RFC][PATCH 1/4] create mm/Kconfig for arch-independent memory options References: <4244D068.3080900@osdl.org> <1111863649.9691.100.camel@localhost> <4245CC80.10306@osdl.org> <1111871303.9691.110.camel@localhost> In-Reply-To: <1111871303.9691.110.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dave Hansen wrote: > On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote: > >>I wasn't trying to catch you, but I've already looked at >>all 4 patches in the series and I still can't find an >>option that is labeled/described as "Sparse Memory".... >>The word "sparse" isn't even in patch 3/4... maybe >>there is something missing? > > > Nope, you're not missing anything. I'm just a little mixed up. You can > find the actual "Sparse Memory" option in this patch: > > http://sr71.net/patches/2.6.12/2.6.12-rc1-mhp2/broken-out/B-sparse-151-add-to-mm-Kconfig.patch > > I could easily remove the references to it in the patches that I posted > RFC, but I hoped that they would get in quickly enough that it wouldn't > matter. Also, the help option does say that all of the options probably > won't show up. So, users shouldn't be horribly confused if they don't > see the sparsemem option. OK, thanks for the clarifications. -- ~Randy