From aafc1dbe4712c86189bbc1d4d54ad8cb4c69be7e Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Mon, 5 Oct 2020 22:27:18 +0200 Subject: New upstream version 1.27.90 --- docs/libnm/html/libnm-nm-utils.html | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) (limited to 'docs/libnm/html/libnm-nm-utils.html') diff --git a/docs/libnm/html/libnm-nm-utils.html b/docs/libnm/html/libnm-nm-utils.html index c94042ff..cca4b08b 100644 --- a/docs/libnm/html/libnm-nm-utils.html +++ b/docs/libnm/html/libnm-nm-utils.html @@ -2117,7 +2117,7 @@ the functionality are encouraged to make their implementations instead.

nm_utils_hwaddr_len (int type);

Returns the length in octets of a hardware address of type type .

-

It is an error to call this function with any value other than +

Before 1.28, it was an error to call this function with any value other than ARPHRD_ETHER or ARPHRD_INFINIBAND.

Parameters

@@ -2137,7 +2137,7 @@ nm_utils_hwaddr_len (int t

Returns

-

the length.

+

the length or zero if the type is unrecognized.

@@ -2228,7 +2228,7 @@ nm_utils_hwaddr_aton (const char< and converts it to binary form in buffer . Bytes in asc - can be sepatared by colons (:), or hyphens (-), but not mixed.

+ can be separated by colons (:), or hyphens (-), but not mixed.

Parameters

@@ -2643,8 +2643,9 @@ characters. If set to nm_utils_inet6_ntop()). Beware, that the internal buffer will be overwritten with ever new call of nm_utils_inet4_ntop() or nm_utils_inet6_ntop() that does not provide its own dst -buffer. Also, -using the internal buffer is not thread safe. When in doubt, pass your own +buffer. Since +1.28, the internal buffer is thread local and thus thread safe. Before +it was not thread safe. When in doubt, pass your own dst buffer to avoid these issues.

@@ -2689,8 +2690,9 @@ characters. If set to nm_utils_inet4_ntop()). Beware, that the internal buffer will be overwritten with ever new call of nm_utils_inet4_ntop() or nm_utils_inet6_ntop() that does not provide its own dst -buffer. Also, -using the internal buffer is not thread safe. When in doubt, pass your own +buffer. Since +1.28, the internal buffer is thread local and thus thread safe. Before +it was not thread safe. When in doubt, pass your own dst buffer to avoid these issues.

@@ -3530,7 +3532,7 @@ generating the dynamic WEP keys automatically

NM_UTILS_INET_ADDRSTRLEN

-
#define NM_UTILS_INET_ADDRSTRLEN     INET6_ADDRSTRLEN
+
#define NM_UTILS_INET_ADDRSTRLEN INET6_ADDRSTRLEN
 

 
Defines the minimal length for a char buffer that is suitable as dst
  argument
-- 
cgit 1.3.0-6-gf8a5