> It doesn't make sense to have a default setting different to that what we > suggest the user to select. Even when configured on at compile time, cleancache functionality is inert unless the hooks are registered by a "backend" (e.g. zcache or Xen or other future code). If configured on, a backend module can dynamically enable cleancache functionality; the cost is extremely small, so all postings of cleancache had "default y". Just before Linus merged cleancache, he insisted that the default be changed to "n". I didn't argue, just changed it. However, I think in the future most distros will prefer to have it set so the functionality can be enabled at runtime, thus the help comment is inconsistent with the default. > Also fixes a typo. Don't know how I missed that one :-} Typo fix: Acked-by: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> Dan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href