On Wed, 2016-04-06 at 13:45 +0200, Paulina Szubarczyk wrote: > Return rc value instead of always 0. > I'd say "Propagate the error, insetad of always returning 0", but yeah, this is nitpicking! :-P
Also, not my call, but I'd include this change inside of patch 1: both are simple enough that they can be made one, IMO (mentioning this new thing being done in the changelog of the resulting patch, of course). > --- a/tools/libxl/libxl_pci.c > +++ b/tools/libxl/libxl_pci.c > @@ -1602,7 +1602,7 @@ int libxl__device_pci_destroy_all(libxl__gc > *gc, uint32_t domid) > } > While you're here, libxl conding style says that the 'int rc' variable used to host libxl error codes, and if necessary, to return them, should not be initialized, while this function does it. Again not my call, but I think you can get rid of the initialization too (and just assign 0 to it before the loop). Regards, Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel