[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 4/7] xen: rename dom0 to hardware_domain



On 03/27/2014 08:20 AM, Egger, Christoph wrote:
On 27.03.14 12:52, Daniel De Graaf wrote:
This should not change any functionality other than renaming the global
variable.  In a few cases (primarily the domain building code), a local
variable or argument named dom0 was created and used instead of the
global hardware_domain to clarify that the domain being used in this
case is actually domain 0.

Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>
Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
Cc: Stefano Stabellini <stefano.stabellini@xxxxxxxxxx>
Cc: Tim Deegan <tim@xxxxxxx>
Cc: Liu Jinsong <jinsong.liu@xxxxxxxxx>
Cc: Christoph Egger <chegger@xxxxxxxxx>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@xxxxxxx>
Cc: Xiantao Zhang <xiantao.zhang@xxxxxxxxx>

These changes are pretty mechanical.
I suppose you have code (or at least a plan) on top of
this patch? Is this a cleanup patch splitted out of it?

Christoph

This is a part of a patch series that allows the hardware domain to be
distinct from the domain with ID 0.  As part of this series, the "dom0"
global variable now refers to the hardware domain, and as such, should
not be named dom0.

You were CC'd on this patch because of the MAINTAINERS entry for mcheck.
Actually, it looks like patch 1 of this series should also have cc'd
you; I neglected to rerun get_maintainer.pl after expanding it.

--
Daniel De Graaf
National Security Agency

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.