On Wednesday, 28 December 2022 14:06:03 CET Greg KH wrote:
These commands will show them too: git log --oneline -25 d1b5749687618d969c0be6428174a18a7e94ebd2 --reverse git log --oneline -1 b136468a0024ea90c1259767c732eed12ce6edba git log --oneline -2 8c701fa6e38c43dba75282e4d919298a5cfc5b05 --reverse git log --oneline -5 9dcd71c863a6f6476378d076d3e9189c854d49fd --reverse
That's a lot, I'll look at them in a week or so after catching up with the rest of the stable queue.
Ok.
Any reason why you all didn't properly mark these for the stable tree beforehand?
Insofar as this was (also) directed at me: I don't know how this works (yet).
I'm an interested 'bystander' who is interested in kernel 6.1 as that'll likely be Debian Bookworm's kernel and rockchip/Pine64 devices.
As such I regularly look at the (6.1) queue and found those rockchip crypto patches. I also tested this whole patch set to see whether it does what it claimed; which it does.
And this is the hotfix, planned for 6.2 (unwrapped): https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/c ommit?id=53e8e1e6e9c1653095211a8edf17912f2374bb03
fix for what?
Rob Herring noted a mismatch between the dt-bindings of the "reset-names" property and the implementation in rk3399.dtsi in commit 8c701fa6e38c here: https://lore.kernel.org/all/CAL_JsqJkHR+iccEf=5SU40Qq+cQpGZRq26TLzec-_Nr-Buu... ("lave" -> "slave" and "crypto" -> "crypto-rst")
I may have used the word 'hotfix' incorrectly.
When will it be sent to Linus?
I don't know, but I've seen several "Merge tag 'vX.Y-rockchip-dtsfixes' ..." commits by Arnd Bergmann around rc6 or rc7 in the past.