Forked from
Reform / reform-boundary-uboot
Source project has a limited visibility.
-
Mike Frysinger authored
The non-reentrant versions of the hashtable functions operate on a single shared hashtable. So if two different people try using these funcs for two different purposes, they'll cause problems for the other. Avoid this by converting all existing hashtable consumers over to the reentrant versions and then punting the non-reentrant ones. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>
Mike Frysinger authoredThe non-reentrant versions of the hashtable functions operate on a single shared hashtable. So if two different people try using these funcs for two different purposes, they'll cause problems for the other. Avoid this by converting all existing hashtable consumers over to the reentrant versions and then punting the non-reentrant ones. Signed-off-by:
Mike Frysinger <vapier@gentoo.org>