Thomas Haller d18f40320d platform: merge NMPlatformError with nm-error ... Platform had it's own scheme for reporting errors: NMPlatformError. Before, NMPlatformError indicated success via zero, negative integer values are numbers from <errno.h>, and positive integer values are platform specific codes. This changes now according to nm-error: success is still zero. Negative values indicate a failure, where the numeric value is either from <errno.h> or one of our error codes. The meaning of positive values depends on the functions. Most functions can only report an error reason (negative) and success (zero). For such functions, positive values should never be returned (but the caller should anticipate them). For some functions, positive values could mean additional information (but still success). That depends. This is also what systemd does, except that systemd only returns (negative) integers from <errno.h>, while we merge our own error codes into the range of <errno.h>. The advantage is to get rid of one way how to signal errors. The other advantage is, that these error codes are compatible with all other nm-errno values. For example, previously negative values indicated error codes from <errno.h>, but it did not entail error codes from netlink.		2018-12-27 21:33:59 +01:00
..
nm-vpn-connection.c	platform: merge NMPlatformError with nm-error	2018-12-27 21:33:59 +01:00
nm-vpn-connection.h	core: improve and fix keeping connection active based on "connection.permissions"	2018-12-09 14:47:32 +01:00
nm-vpn-manager.c	core,clients: use our own string hashing function nm_str_hash()	2017-10-18 13:05:00 +02:00
nm-vpn-manager.h	build: rename "src/vpn-manager" to "src/vpn"	2016-11-21 14:07:47 +01:00