Juergen Fitschen

I'd say the glob is the cleanest solution. Integrating wireguard-specific stuff into babeld feels a little bit wrong to me. I love babeld for its simplicity - it just needs...

Great PR! I like it :) First test: samr30-pro ```diff diff --git a/boards/samr30-xpro/Makefile.dep b/boards/samr30-xpro/Makefile.dep index 4224c14c79..4afbe80d4c 100644 --- a/boards/samr30-xpro/Makefile.dep +++ b/boards/samr30-xpro/Makefile.dep @@ -5,3 +5,6 @@ endif ifneq (,$(filter saul_default,$(USEMODULE))) USEMODULE...

What's the current state of this documentation? Is this ready to be reviewed? I cloud do a *try to understand what you're describing and point out what's unclear to me*...

Oh don't worry - I really don't want to put any pressure onto you. Take the time you need. I'm just keen to get Kconfig in - doing all the...

Sneak peak: I'm completely aware of `ztimer_acquire()` and `ztimer_release()` introducing more complexity. But this interface could be just a foundation for something like this: ztimer_watch ```c typedef struct { ztimer_now_t...

Thank you for your response! Yes, I agree that setting up a `ztimer_t` with a very long offset can also be a solution to make the `pm_layered` approach work. But...

An addition to the wrapped ztimer_now() values - I just understood your point after reading your response a second time: If there must the guarantee that it hasn't wrapped during...

Some additional work: I've introduced `ztimer_ondemand_strict` with 04607ed. It will make sure `ztimer_now()` is only called if the timer is active. Of course, this pseudomodule brakes almost every module using...

Would anybody mind if I squash commits? I think I have finished for the first round and implemented everything necessary for the `ztimer_ondemand` driver to work properly.

And squashed. I'd say this PR is ready to be reviewed. I've fixed typos and added some breaks to long lines. Static tests are green now.