summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2014-08-20 16:13:52 -0400
committerDan Winship <danw@gnome.org>2014-08-20 16:14:15 -0400
commit449ff11b78db6d5ec3388c57a2f1f871cf0f26d7 (patch)
tree27163c72ac700c2f3f0f4b8bada40d9567f4d437
parent32a53f786d269ea2cc7f1998fd5e6b07a144db70 (diff)
libnm-core: clarify a comment about InfiniBand hardware address matching
-rw-r--r--libnm-core/nm-utils.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/libnm-core/nm-utils.c b/libnm-core/nm-utils.c
index aeb2063a38..4304b5b683 100644
--- a/libnm-core/nm-utils.c
+++ b/libnm-core/nm-utils.c
@@ -2133,8 +2133,9 @@ nm_utils_hwaddr_valid (const char *asc, gssize length)
*
* 3. If @hwaddr1 and @hwaddr2 are InfiniBand hardware addresses (that is, if
* they are %INFINIBAND_ALEN bytes long in binary form) then only the last
- * 8 bytes are compared, since those are the only bytes that matter for
- * InfiniBand hardware address matching.
+ * 8 bytes are compared, since those are the only bytes that actually
+ * identify the hardware. (The other 12 bytes will change depending on the
+ * configuration of the InfiniBand fabric that the device is connected to.)
*
* If a passed-in ASCII hardware address cannot be parsed, or would parse to an
* address larger than %NM_UTILS_HWADDR_LEN_MAX, then it will silently fail to