History log of /external/libnl/lib/cache_mngt.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
6782b6f709d03877a5661a4c8d8f8bd1b461f43f 10-Dec-2008 Thomas Graf <tgr@plip.localdomain> restructure module documentation order

split hiearchy into one top level module per library
8a3efffa5b3fde252675239914118664d36a2c24 14-May-2008 Thomas Graf <tgr@lsx.localdomain> Thread-safe error handling

In order for the interface to become more thread safe, the error
handling was revised to no longer depend on a static errno and
error string buffer.

This patch converts all error paths to return a libnl specific
error code which can be translated to a error message using
nl_geterror(int error). The functions nl_error() and
nl_get_errno() are therefore obsolete.

This change required various sets of function prototypes to be
changed in order to return an error code, the most prominent

struct nl_cache *foo_alloc_cache(...);
changed to:
int foo_alloc_cache(..., struct nl_cache **);

struct nl_msg *foo_build_request(...);
changed to:
int foo_build_request(..., struct nl_msg **);

struct foo *foo_parse(...);
changed to:
int foo_parse(..., struct foo **);

This pretty much only leaves trivial allocation functions to
still return a pointer object which can still return NULL to
signal out of memory.

This change is a serious API and ABI breaker, sorry!
358e44efa4b6791943acd26d4f9ad85771c6830c 05-Mar-2008 Thomas Graf <tgr@deb.localdomain> Optimize nl_cache_ops_associate by checking protocol early
d36d396fd0ae94aa2269546a02b5973b4ec27775 11-Oct-2007 Thomas Graf <tgraf@suug.ch> Cache message type association interface cleanups
44d362409d5469aed47d19e7908d19bd194493a4 15-Sep-2007 Thomas Graf <tgraf@suug.ch> Initial import