On 5/31/18 4:48 PM, Stefano Stabellini wrote: > One note about Kconfig renaming: I can see the benefit of being > consistent with the naming and using HAS_ only for options that are > always enabled, but I really don't have a strong opinion on this topic.
So fwiw, the HAS_ fields come from the Linux kernel. Its mostly used to let the build system know that this hardware HAS this ability and then later there is an option to allow it to be configured on and off. Our use of Kconfig didn't actually introduce these. The Xen build system relied on them before I added Kconfig since we sync a number of drivers over from the Linux kernel tree. It just felt natural to move them out of being hard coded values in the Makefiles and into Kconfig proper so they could be used as Linux uses them. -- Doug Goldstein _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
