![]() | |||||||||||||
Messages in this thread |
On Mon, 19 Mar 2007 00:44:43 +0000 Ralf Baechle <ralf@linux-mips.org> wrote: > On Sun, Mar 18, 2007 at 08:36:48PM -0400, Alan Stern wrote: > > > Acked-by: Alan Stern <stern@rowland.harvard.edu> > > > > Thank you for spotting and fixing this. > > It's the second time I've fixed a CONFIG_SYSFS=n bug. Of course that > sort of thing just shouldn't happen - but the fact that in both cases > the bug wasn't noticed for a few days makes me wonder if we simply should > always enable CONFIG_SYSFS at some point. > If is a bit of a pain to maintain CONFIG_SYSFS=n. But then, it's realtively easy to fix things when they do break, and sysfs does consume rather a lot of memory at runtime. Hopefully someone out there is finding SYSFS=n to be useful for deeply embedded applications. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-03-19 07:07 [from the cache] ©2003-2008 | |||||||||||||