On 2021-07-13 13:57, [email protected] wrote: > > This is particularly useful in multithreaded non-C FFI, where > additional context from where the event handler was registered may be > critical to ensuring the output of the event is sent to the right > location. > > Signed-off-by: Louis Hampton <[email protected]> In order to get the additional context, the normal solution is to embed struct ubus_event_handler into another data structure, which contains the extra context and can be accessed via container_of. Is there a reason why this can't be done in your code as well?
- Felix _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
