summaryrefslogtreecommitdiff
path: root/libnm-core/nm-setting-user.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-15 16:52:32 +0100
commitdb3240b97147068bff52f2ff140e3f0bb7f60767 (patch)
treed12849cb6147a3841d53648bd98252719f495324 /libnm-core/nm-setting-user.c
parent8e37d536bd01081487cbb61114f6fb4bd61c7baa (diff)
downloadNetworkManager-th/nm-hash-all.tar.gz
all: use nm_str_hash() instead of g_str_hash()th/nm-hash-all
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-core/nm-setting-user.c')
-rw-r--r--libnm-core/nm-setting-user.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libnm-core/nm-setting-user.c b/libnm-core/nm-setting-user.c
index 049607e146..526bbd2073 100644
--- a/libnm-core/nm-setting-user.c
+++ b/libnm-core/nm-setting-user.c
@@ -210,7 +210,7 @@ nm_setting_user_check_val (const char *val, GError **error)
static GHashTable *
_create_data_hash (void)
{
- return g_hash_table_new_full (g_str_hash, g_str_equal, g_free, g_free);
+ return g_hash_table_new_full (nm_str_hash, g_str_equal, g_free, g_free);
}
/**