| To: | C Michael Sundius <Michael.sundius@sciatl.com> |
|---|---|
| Subject: | Re: sparsemem support for mips with highmem |
| From: | Dave Hansen <dave@linux.vnet.ibm.com> |
| Date: | Fri, 15 Aug 2008 09:20:57 -0700 |
| Cc: | Thomas Bogendoerfer <tsbogend@alpha.franken.de>, linux-mm@kvack.org, linux-mips@linux-mips.org, jfraser@broadcom.com, Andy Whitcroft <apw@shadowen.org> |
| In-reply-to: | <48A5AADE.1050808@sciatl.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <48A4AC39.7020707@sciatl.com> <1218753308.23641.56.camel@nimitz> <48A4C542.5000308@sciatl.com> <20080815080331.GA6689@alpha.franken.de> <1218815299.23641.80.camel@nimitz> <48A5AADE.1050808@sciatl.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Fri, 2008-08-15 at 09:12 -0700, C Michael Sundius wrote: > One thing that I had thought about and also came up when my peers here > reviewed my changes was that we probably could put those bit numbers > (at the very least the segment size) in the .config file. > > we decided that the power that be might have had a reason for that and > we left it not wanting to meddle with the other arch's. > > Dave, do you have a comment about that? Doing it with Kconfig would be fine with me. It would be an excellent place to add that help text. Although, I'm not sure that it should be something that is interactive. Probably just strictly take the place of the #defines we already have. -- Dave |
| Previous by Date: | Re: sparsemem support for mips with highmem, C Michael Sundius |
|---|---|
| Next by Date: | Re: sparsemem support for mips with highmem, Thomas Bogendoerfer |
| Previous by Thread: | Re: sparsemem support for mips with highmem, C Michael Sundius |
| Next by Thread: | Re: sparsemem support for mips with highmem, Thomas Bogendoerfer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |