On 03/13/2013 10:07 AM, Seth Forshee wrote: >> >> Granted, this change does mean that your decision at compile time may be >> final, and you can't enable the pstore code at runtime if you built your >> kernel/efivars module with CONFIG_EFI_VARS_PSTORE=n. Arguably, I think >> that's a feature that some people will want, e.g. "Don't allow enabling >> the efivars pstore backend at all... no, srsly!". > > Hmm. Since my original patch was to compile pstore support out > completely, I interpreted Peter's suggestion to be allowing the user > override the default even if the default is disabled. That's the > assumption my implementation was based off of, but maybe I > misunderstood. > > But if Peter agrees with your changes then I'm fine with them too. > I think there should be two compile-time options (one to compile in the EFI pstore code at all, and one to set its default.) -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
