What was the reason to split these? Why can't we just have a consistent
CONFIG_XEN (provided in arch/*/Kconfig), and derive all
architecture-specific information from other CONFIG_* values? Main
reason for the question is the (apparently) inconsistent use of one or
the other in various places.
Thanks, Jan
_______________________________________________
Xen-merge mailing list
Xen-merge@lists.xensource.com
http://lists.xensource.com/xen-merge
CONFIG_XEN (provided in arch/*/Kconfig), and derive all
architecture-specific information from other CONFIG_* values? Main
reason for the question is the (apparently) inconsistent use of one or
the other in various places.
Thanks, Jan
_______________________________________________
Xen-merge mailing list
Xen-merge@lists.xensource.com
http://lists.xensource.com/xen-merge