On Tue, Aug 23, 2016 at 01:59:10AM +0200, Luis R. Rodriguez wrote: > On Fri, Aug 19, 2016 at 03:10:33PM -0700, Kees Cook wrote: > > On Fri, Aug 19, 2016 at 2:32 PM, <mcg...@kernel.org> wrote: > > > diff --git a/init/Kconfig b/init/Kconfig > > > index cac3f096050d..ef09e83b9196 100644 > > > --- a/init/Kconfig > > > +++ b/init/Kconfig > > > @@ -53,6 +53,28 @@ config CROSS_COMPILE > > > need to set this unless you want the configured kernel build > > > directory to select the cross-compiler automatically. > > > > > > +config BUILD_AVOID_BITROT > > > + bool "Enable force building of force-obj-y and force-lib-y" > > > > Sorry to continue the bikeshedding on this, but if I encounter > > something in a Makefile named "force-obj-y" I would expect it to > > always be built, no matter what. But this is not the case: the > > "force-" prefix is tied to this CONFIG_BUILD_AVOID_BITROT. This verb > > usage is weird, as I'd expect an adjective, like "forceable-obj-y" or > > something that describes that it CAN be built even with the CONFIG for > > it is missing, etc. > > > > Regardless, I defer to Michal on this, but I'm not a fan of "force" > > being used when it's an optional action. :) > > Sure, Michal let me know if forceable-obj-y and forceable-lib-y is the > way to go.
Michal? Any preference ? Or how about opt-force-obj ? Luis _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
