zarzarzar has quit [Read error: Connection reset by peer]
fblaese has quit [Server closed connection]
fblaese has joined #openwrt-devel
Rondom has joined #openwrt-devel
danitool has joined #openwrt-devel
gladiac has quit [Server closed connection]
gladiac has joined #openwrt-devel
digitalcircuit has quit [Server closed connection]
digitalcircuit has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
gladiac is now known as Guest1121
gladiac has joined #openwrt-devel
Guest1121 has quit [Ping timeout: 480 seconds]
rua has quit [Quit: Leaving.]
rua has joined #openwrt-devel
yolo has quit [Remote host closed the connection]
goliath has joined #openwrt-devel
<rsalvaterra>
jow, hauke, any objections on merging my almost-two-year-old procd patches, dropping support for mounting /tmp on a zram block device? It would be nice to get rid of that…
<jow>
rsalvaterra: no objections
<jow>
nbd: I am trying to understand ubus_notify_async()
<jow>
nbd: do I eventually need to call ubus_{complete/abort}_request() on struct ubus_notify_request.req or will the complete_cb get invoked once all subscribers replied (or timed out) ?
<jow>
background is that I currently write a binding for this api and I try to understand the lifecycle/memory model of the struct ubus_notify_request context
<jow>
I /guess/ that ubus_complete_request() can be used to synchroneously await the completion of the notify request (capped to the given timeout)
<jow>
so I likely don't need it for an async api
<jow>
and I suppose ubus_abort_request() can be used on async notify requests to prematurely cancel the req, e.g. from within a data callback
<jow>
hmm, I guess I need to invoke ubus_complete_request_async() before handing control back to the event loop
<jow>
Ah, found it in the examples. Thanks for the passive rubber ducking
wvdakker has quit [Ping timeout: 480 seconds]
bkallus has joined #openwrt-devel
shibboleth has joined #openwrt-devel
wvdakker has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
rua has joined #openwrt-devel
<rsalvaterra>
jow: Ok, thanks! Will merge later today.
<rsalvaterra>
I'll squash the ones for the openwrt tree, though. Doesn't really make sense to have two patches, now that I looked at them again. :)
bkallus has quit [Ping timeout: 480 seconds]
<mangix>
Cool. I can stop carrying them.
<Slimey>
nothing like doing software updates to firewalls and having a hardware failure right in the middle
goliath has quit [Quit: SIGSEGV]
Grommish has joined #openwrt-devel
rua has quit [Ping timeout: 480 seconds]
<Grommish>
Is there a CONFIG_ flag for -fPIC?
<Grommish>
Oh, it's just automatic and on all the time?
<karlp>
$(FPIC) so it does the right thing on all targets, but yeah,
linusw__ has joined #openwrt-devel
linusw__ has quit []
linusw__ has joined #openwrt-devel
rua has joined #openwrt-devel
Grommish_ has joined #openwrt-devel
rua has quit [Quit: Leaving.]
Grommish has quit [Ping timeout: 480 seconds]
<Grommish_>
karlp: Thanks.. That's what it looked like but I wanted to confirm