summaryrefslogtreecommitdiff
path: root/libnm/nm-device.c
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2017-11-15 16:06:43 +0100
committerThomas Haller <thaller@redhat.com>2017-11-16 11:49:52 +0100
commita6be2f4aa9070e7f423b7c9992dbae51f092071e (patch)
tree8e744859bc7dc51e78c586f9a290992149833a32 /libnm/nm-device.c
parent93adadbdcbbccfeafb8523b129f103bb5b23f7d5 (diff)
downloadNetworkManager-a6be2f4aa9070e7f423b7c9992dbae51f092071e.tar.gz
all: use nm_str_hash() instead of g_str_hash()
We also do this for libnm and libnm-core, where it causes visible changes in behavior. But if somebody would rely on the hashing implementation for hash tables, it would be seriously flawed.
Diffstat (limited to 'libnm/nm-device.c')
-rw-r--r--libnm/nm-device.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libnm/nm-device.c b/libnm/nm-device.c
index 65afd078dc..5e4c789394 100644
--- a/libnm/nm-device.c
+++ b/libnm/nm-device.c
@@ -2570,7 +2570,7 @@ nm_lldp_neighbor_new (void)
neigh = g_new0 (NMLldpNeighbor, 1);
neigh->refcount = 1;
- neigh->attrs = g_hash_table_new_full (g_str_hash, g_str_equal, g_free,
+ neigh->attrs = g_hash_table_new_full (nm_str_hash, g_str_equal, g_free,
(GDestroyNotify) g_variant_unref);
return neigh;