[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v2 00/10] xl: improve coding style and return more failure on failure for more xl commands
This is my bite-sized outreachy project [1][2]. The patch aims to improve coding_style and return failure for more xl commands: - pci-* -- tmem-* After rebase to staging it seems that the patch {09} cleaning libxl_set_memory_target() to return useful error codes from [0] is not applied I resent it here. In pci-* functions libxl__create_pci_backend(), libxl__device_pci_destroy_all() error codes are returned instead of always 0. Int the changes I follow CODING_STYLE as in the coresponding patches: - In general, don't initialize rc / r, but use set-and-goto - Use 'r' for non-libxl error codes - Use EXIT_FAILURE and EXIT_SUCCESS in main_foo() - Use 1 and 0 in internal functions of xl [0] http://lists.xenproject.org/archives/html/xen-devel/2015-12/msg02246.html [1] http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03031.html [2] https://www.mail-archive.com/xen-devel@xxxxxxxxxxxxx/msg62055.html Changed since v1: * Make libxl__device_from_pcidev() return void instead 0. * Modify the libxl_device_pci_assignable_list() function to use only one 'out' cleaning path. * Changed exit() calls to 'return 1;' for set_memory_* and pci_* functions in xl_cmdimpl * Added the error cleanup path 'out' in libxl_tmem_* functions and replaced return with set-and-goto statements. * Use 'lrc' for return values to local functions libxl__* _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |