00:30 <SlimeyX> any words of wisdom? :P https://forum.openwrt.org/t/adding-openwrt-support-for-adtran-bluesocket-bsap-3040/164981/4

03:15 <owrt-images-builds> Build [#47](https://buildbot.staging.openwrt.org/images/#/builders/89/builds/47) of `openwrt-23.05_apm821xx/nand` failed.

03:37 <KGB-0> https://tests.reproducible-builds.org/openwrt/openwrt_lantiq.html has been updated. (95.9% images and 99.9% packages reproducible in our current test framework.)

07:04 <RoganDawes> trying to figure out the correct way to enable things like CONFIG_XXHASH. I see a bunch of places have it in the config-5.15 or config-6.1 files, but there is also a KernelPackage definition for lib-zstd in package/kernel/linux/modules/lib.mk

07:06 <RoganDawes> (context is enabling UBI and UBIFS for my Wink Hub)

07:07 <RoganDawes> so far I have the ubifs support enabled, but I had to enable UBI directly in the config-5.15 file

08:03 <PaulFertser> RoganDawes: if you need some option for the rootfs then you need it in target config.

08:14 <mrkiko> rsalvaterra: do youthink the last fit uimage fix dangole pushed to mediatek 6.1 bump PR may fix the RT3200?

08:15 <rsalvaterra> mrkiko: Good news, fixed mine, yes. Already gave dangole feedback about it. :)

08:15 <rsalvaterra> Running 6.1.38 as we speak.

08:16 <mrkiko> rsalvaterra: great!!

08:16 <rsalvaterra> The FIT partition parser patches got broken in the rebasing process, that's why the rootfs couldn't be mounted.

08:18 <mrkiko> rsalvaterra: great it's fixed now. I might try the PR as well or just wait for it to bemerged, I don't know

09:25 <mrkiko> rsalvaterra: ok, running 6.1.37 atm

09:27 <rsalvaterra> Nice! :)

15:20 <raenye> Does it make sense to create an issue or a PR for fixing a Makefile typo?

15:20 <raenye> https://github.com/openwrt/openwrt/blob/0dc0504fc8e5f0c3cafe6c1da7192f51a09c5bc3/target/linux/apm821xx/modules.mk#L26

15:21 <raenye> Wrong autoloaded module in /etc/module.d

15:29 <Lynx-> Possible to amend commit messages on a pull request on your repo by force pushing to the fork?

15:30 <Lynx-> I know I can add further commits to branch on fork and that those get brought into the pull request, but what if I want to change certain commit messages?

15:30 <Lynx-> is that also possible?

15:36 <tmn505> raenye: does not make sense to create issue if You know how to fix it and have skill to do it (unless the change doesn't fix the issue). Make a PR and add 'Fixes: 55fbcad20a2d (apm821xx: make crypto4xx as a standalone module)' before Your SoB in commit message.

15:38 <raenye> tmn505: Already fixed in my local tree; shall create a PR, thanks.

15:40 <dev1ce> anyone can take care of asu server? cant build fw rn

15:43 <raenye> tmn505: https://github.com/openwrt/openwrt/pull/13068

15:47 <raenye> Lynx-: you could git rebase -i and change the order so a particular commit would be first. Then git commit --amend it.

15:47 <Lynx-> raenye but can I do this on fork

15:48 <raenye> Lynx-: not sure what you mean. I usually fix everything on my local tree, then force push to my fork on github, which updates the PR

15:49 <Lynx-> ah I am refering to someone else's pull request

22:35 <bluecmd[m]> For your consideration; https://github.com/openwrt/openwrt/pull/13071

22:37 <bluecmd[m]> Also, is there any way I can push my PR https://github.com/openwrt/openwrt/pull/13039 forward? I'd love to have it merged so I can continue with filing PRs for e.g. sys upgrades

23:11 <Mangix> bluecmd[m]: maybe hauke can help

23:11 <Mangix> there are 350 PRs open. quite backed up.

23:16 <bluecmd[m]> Yes indeed, I understand it's hard and thankless work. I'm just worried that the PR will fall to far behind and never get merged. I've put quite a lot of effort splitting things out and selecting isolated parts that are hopefully easy to merge, so my hope is that it's just a matter of finding the right person to press the button after a hopefully straight forward review.

23:16 <bluecmd[m]> But what do I know, first time contributor to openwrt

23:39 <Mangix> bluecmd[m]: only thing I see off is the commit message. Maybe model after: https://github.com/openwrt/openwrt/commit/c9cb6411c1a70516d5922e88c45b338de041baba

23:42 <bluecmd[m]> So basically copy the current state of https://openwrt.org/inbox/toh/cisco/vedge_1000? Seems odd to me, but if that's how the maintainers want it then sure.

23:42 <Mangix> blocktrron is one so :shrug:

23:43 <bluecmd[m]> As you can see from the wiki it's quite a lot of details e.g. regarding how to use JTAG and so on, including pictures which can't obviously be part of the message. So not sure how useful it would be, but again if that's desired I'll oblide

23:46 <bluecmd[m]> That said, thanks for looking at the PR!

23:48 <Mangix> this was mine: https://github.com/openwrt/openwrt/commit/f4eef5f2a18400bc7f548d629e1d5825a2b26e5a

23:50 <Mangix> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e7b813b32a42a3a6281a4fd9ae7700a0257c1d50 is interesting. I wonder if urandom-seed should be modified to use ubootenv for its seeds

23:54 <Mangix> rmilecki: ^^