08:24 <arnd> ardb, krzk, robher: I wonder if I'm being too pedantic about that loongarch suspend patch at https://lore.kernel.org/all/19feb595-e22a-4304-9b88-b5cb55949cd8@app.fastmail.com/ since krzk has already reviewed the binding, and the ACPI variant uses the same method

08:25 <arnd> it just feels wrong to have the suspend function just branch into an address provided in a DT property to have it execute code from ROM

08:26 <arnd> <insert exploit vector here>

08:35 <geertu> arnd: If an attacker can tamper with the DTB, you have to consider the device compromised anyway.

08:36 <arnd> geertu: sure, it's just that we usually don't go out of our way to make it easy

08:48 <geertu> arnd: Seeing you will be on holidays soon, do you have a backup for handling late soc PRs?

08:49 <arnd> geertu: no, my plan is to travel with a laptop and still do the important merges.

08:49 <geertu> arnd: IC ;-)

08:50 <geertu> I do hope no urgent and important things show up, and we can just postpone to v6.7.

08:54 <arnd> Right, I think the merge window will be fairly quiet because of the vacation and I've already merged a lot, thanks to a lot of you all sending pull requests early, thanks for that!

09:40 <geertu> arnd: Enjoy your holidays!

09:40 <arnd> thanks

10:09 <conchuod> arnd: I looked at the loongarch thing in one of the first revisions & neither did I like it nor was I able to get the chap to explain what the firmware actually was doing.

16:28 <broonie> arnd: Is https://lore.kernel.org/all/20230712-arm-tlv320aic31xx-config-v1-1-2422142cb88d@kernel.org/ on your radar?

16:29 <tlwoerner> how can i find out if a trivial patch i sent at the beginning of august has been picked up?

16:29 <tlwoerner> i don't need a reply to a small patch, but if there is no reply does that mean is slipped through without being noticed?

16:30 <arnd> broonie: it looks like I merged it two days ago, it just hasn't shown up in linux-next yet

16:31 <broonie> Ah, great - don't think I got email for it but it might've been lost in the noise. Thanks!

16:32 <arnd> tlwoerner: it depends on the maintainer. If it's a patch you sent to soc@kernel.org, there is a patchwork instance that shows the status. Some other trees have the same, but I think most don't

16:32 <tlwoerner> oh! there was a reply. odd gmail hasn't informed me

16:32 <tlwoerner> https://lore.kernel.org/linux-arm-kernel/20230809071404.GA11676@atomide.com/

16:33 <rfs613> that's a gmail "feature" :-)

16:33 <tlwoerner> lol

16:36 <arnd> broonie: I see an automated reply to your patch that was sent to:broonie@kernel.org, cc:soc@kernel.org, but it looks like patchwork no longer puts everyone else on cc

16:36 <arnd> so the lakml archive doesn't have it

16:36 <broonie> It probably got lost in a big batch of patchwork stuff.

16:37 <tlwoerner> arnd: get_maintainer didn't tell me to send it to soc@ but rather to linux-omap@

16:37 <tlwoerner> weird, i can't seem to coax gmail into showing me the reply to that patch

16:37 <broonie> It probably got eaten by gmail's spam filtering, it's notoriously fickle at rejecting incoming mail.

16:38 <arnd> tlwoerner: right, we haven't come up with a way to make get_maintainer do the right thing here. Most defconfig changes should go through a platform tree when they are only relevant to one platform, including changes to the generic defconfig but change platform specific drivers

16:38 <arnd> your patches were not platform specific, and crossed multiple files, so soc@kernel.org is in fact the right address for those.

16:39 <tlwoerner> arnd: i wasn't sure if it make sense to split the patch by config option or platform. i chose config option (i chose wrong, lol)

16:39 <arnd> broonie: my entire email setup has improved a lot after I started paying for fastmail.com

16:40 <arnd> tlwoerner: no, I like the way you split it, it makes much more sense to have this change cross multiple files

16:40 <broonie> Incoming stuff seems to work fine and it'd be enormous hassle to omve.

16:48 <tlwoerner> arnd: okay. can i leave it with you, or would you like me to resend?

16:50 <arnd> tlwoerner: the mips changes need an Ack from Thomas Bogendoerfer <tsbogend@alpha.franken.de>, he's Fleedwood on #mipslinux but currently not logged in there.

16:51 <arnd> similarly for the loongarch changes from their maintainers

16:51 <arnd> tlwoerner: it might be easier if you can resend just the arm bits to soc@kernel.org

16:51 <tlwoerner> arnd: okay, will do. thanks!