Peter Bigot d489765be4 net: dhcp: correct timeout scheduling with multiple interfaces ... If there are multiple interfaces a change to the timeout for one cannot determine the correct delay until the next timeout event. That can be determined only by checking for the next event over all interfaces, which is exactly what's done by the timeout worker. Refactor interface timeout configuration to just set the start time and request time, and trigger the worker to calculate the next scheduled event. Signed-off-by: Peter Bigot <peter.bigot@nordicsemi.no>		2021-01-04 10:02:58 +02:00
..
ip	net: dhcp: correct timeout scheduling with multiple interfaces	2021-01-04 10:02:58 +02:00
l2	bluetooth: Convert DEVICE_AND_API_INIT to DEVICE_DEFINE	2020-12-19 20:01:42 -05:00
lib	net: dns: review use of k_work APIs	2021-01-04 10:01:47 +02:00
buf.c	kernel: subsys: lib: drivers: Use k_heap instead of z_mem_pool wrappers	2020-12-07 21:50:14 -05:00
CMakeLists.txt
hostname.c	net: hostname: define public macro representing maximum hostname length	2020-11-17 19:21:43 -05:00
Kconfig	power: standarize PM Kconfigs and cleanup	2020-12-09 15:18:29 -05:00
Kconfig.hostname
Kconfig.template.log_config.default.net
Kconfig.template.log_config.net