08:49 <wens> getting a lot of "Misaligned patch-site" warnings on next-20230130, is that normal?

09:39 <bjdooks> tagr: we've not got very far with asking our nvidia contacts for help with wifi

10:03 <arnd> I need some assembler help: I have a config that results in arch/arm/mm/proc-v7.S failing to get assembled, apparently the "adr r3, v7_crval" is just out of range for the +/-1024 byte range. gas tells me "Error: invalid constant (fffffffffffffbf4) after fixup", while clang integrated-as says "error: out of range pc-relative fixup value"

10:04 <ardb> arnd: adr_l ?

10:05 <bjdooks> or just move the v7_crval nearer

10:05 <ardb> ukleinek: adr_l is a macro

10:06 <ardb> ukleinek: adrl is a pseudo-instruction but it does not exist in thumb2

10:06 <arnd> adr_l works, but I still don't understand what is actually happening: the definition of v7_crval is in a different file, so I don't see where it even gets the offset from

10:07 <arnd> or why I run into this on linux-next now, but not on older releases

10:07 <ardb> arnd: that other file is #include'd no?

10:07 <arnd> ardb: ok, that explains it

10:16 <arnd> found it: git bisect run points to 84fc86360623 ("ARM: make ARCH_MULTIPLATFORM user-visible"), and the broken config had all the CONFIG_ARM_ERRATA enabled that are in the middle of the file and were previously hidden by ARCH_MULTIPLATFORM