Dear Mike Frysinger,
In message 1291807565-4831-1-git-send-email-vap...@gentoo.org you wrote:
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
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
On Wednesday, December 08, 2010 06:26:04 Mike Frysinger wrote:
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
Dear Joakim Tjernlund,
In message
of280890af.2970da02-onc12577f3.004474f0-c12577f3.0044d...@transmode.se you
wrote:
oh, and this does shrink the final u-boot a little, so that's good
-mike
Nice, over the last years I have noticed that u-boot has grown a lot.
I had to disable a few non
Wolfgang Denk w...@denx.de wrote on 2010/12/08 15:23:17:
Dear Joakim Tjernlund,
In message
of280890af.2970da02-onc12577f3.004474f0-c12577f3.0044d...@transmode.se you
wrote:
oh, and this does shrink the final u-boot a little, so that's good
-mike
Nice, over the last years I have
On Wednesday, December 08, 2010 07:31:54 Joakim Tjernlund wrote:
On Wednesday, December 08, 2010 06:26:04 Mike Frysinger wrote:
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
6 matches
Mail list logo
