**** BEGIN LOGGING AT Fri Dec 27 02:59:57 2019
Dec 27 07:20:46 <blogic> rmilecki: it used to work 6 years ago
Dec 27 07:20:53 <blogic> not tested it in ages
Dec 27 07:56:26 <rmilecki> blogic: ok
Dec 27 12:52:44 <stintel> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next&id=710d7fbe21ee2ceab121f1f84a20edf68f9f9742 --> octeon network driver deleted :/
Dec 27 12:53:59 <olmari> Daumn
Dec 27 12:54:11 <stintel> guess it's time to retire my ERLs
Dec 27 13:42:25 <Hauke> greearb_: someone reports a regression in the ath10k-ct firmware  starting with firmware-5-ct-full-community-12.bin-lede.008 here: https://bugs.openwrt.org/index.php?do=details&task_id=2614#comment7346
Dec 27 14:04:45 <ynezz> can someone more familiar with the sendmsg API take a look at the following patch https://patchwork.ozlabs.org/patch/1215719/ ?
Dec 27 14:16:49 <Hauke> ynezz: I do not uderstand why the fd is in this struct at all in the original code
Dec 27 14:17:03 <ynezz> rather v2 https://patchwork.ozlabs.org/patch/1215721/
Dec 27 14:17:24 <ynezz> Hauke: it's being passed along?
Dec 27 14:19:01 <Hauke> ynezz: ah yes ow I get it
Dec 27 14:19:04 <Hauke> *now
Dec 27 14:19:10 <PaulFertser> Hauke: fyi, some of ath79-tiny devices will have non-working sysupgrade due to my 4k patch :/ I'm working on collecing all the info and will post to the mailing list hopefully this evening. In short: there's no easy proper solution thanks to tp-link using different flash ICs on some "same model" boards.
Dec 27 14:43:39 <hexa-> I have interface in `ubus call network.wireless status` that are missing an ifname key/value, which results in the prometheus-exporter not iterating over those vaps
Dec 27 14:43:53 <hexa-> where is the code behind that?
Dec 27 15:14:02 <PaulFertser> gch981213: ping. Wanted a preliminary discussion of my flash ic findings wrt tplink devices.
Dec 27 18:44:26 <owrt-snap-builds> build #190 of lantiq/xrx200 is complete: Failure [failed images]  Build details are at http://buildbot.openwrt.org/master/images/builders/lantiq%2Fxrx200/builds/190  blamelist: Adrian Schmutzler <freifunk@adrianschmutzler.de>, Felix Fietkau <nbd@nbd.name>, Eneas U de Queiroz <cotequeiroz@gmail.com>, Jason A. Donenfeld <Jason@zx2c4.com>
Dec 27 19:10:23 <ldir> hmm - logread -ENOWORKY
Dec 27 19:12:32 <PaulFertser> ldir: known issue, see mailing list.
Dec 27 19:12:40 <PaulFertser> Being taken care of
Dec 27 19:13:06 <ldir> is there a test patch to test
Dec 27 19:21:11 <ldir> I'm reverting the ubus bump in my local build
Dec 27 19:22:05 <jmv200> A bit confused, is fastpath
Dec 27 19:22:20 <jmv200> software flow offload active on master?
Dec 27 19:33:45 <owrt-snap-builds> build #185 of octeon/generic is complete: Failure [failed images]  Build details are at http://buildbot.openwrt.org/master/images/builders/octeon%2Fgeneric/builds/185  blamelist: Adrian Schmutzler <freifunk@adrianschmutzler.de>, Felix Fietkau <nbd@nbd.name>, Eneas U de Queiroz <cotequeiroz@gmail.com>, Jason A. Donenfeld <Jason@zx2c4.com>
Dec 27 20:02:23 <ynezz> ldir: https://patchwork.ozlabs.org/patch/1215721/
Dec 27 20:52:55 <ldir> ynezz: I reverted the ubus update, which fixed logread... as I'm sure that patch does too... but I also still encountered the nlbwmon & collectd not starting problem
Dec 27 20:53:16 <ldir> I offer that as an observation and not as a complaint.
Dec 27 20:55:18 <ldir> and it maybe suggests there is more than 1 problem... and indeed looking at libubox, maybe the 'problem' is that it's catching malformed messages.
Dec 27 20:58:57 <ynezz> as always, you fix one issue and get three more as a bonus :)
Dec 27 21:00:03 <ldir> so if you could just re-write the kernel while you're there that would be really handy ;-)
Dec 27 21:02:43 <blogic> :-)
Dec 27 21:04:05 <ldir> ynezz: well the other rule is 'don't check for a condition you don't know how to handle, especially one that should never happen' :-)
Dec 27 21:06:24 <Hauke> ynezz: the sendmsg stuff looks ok to me, I looked closely at one of the functons and did similar stuff at work some months ago, but do not have the code at hand to compare now, but it should be similar
Dec 27 21:07:51 <Hauke> your solution looks much more like you should do it when reading the manpage
Dec 27 21:14:10 <ynezz> Hauke: thanks a lot!
Dec 27 21:27:41 <pkgadd> stintel: the relevant threads were http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2019-December/140440.html and http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2019-December/140526.html
Dec 27 21:32:07 * ldir calls it a night - been up since 0500
Dec 27 21:54:39 <Slimey> another build error i dont understand https://paste.ubuntu.com/p/4r5g5fvZ4C/
Dec 27 21:58:49 <ynezz> Slimey: its just a bad luck, try again with latest master
Dec 27 22:02:02 <Slimey> k ill try again and report
**** ENDING LOGGING AT Sat Dec 28 02:59:57 2019