Hi! You may have noticed in the news something funny is going on with umn.edu commits. Researchers at umn.edu did 3 bad-faith patches to kernel, sent them from gmail.com addresses, and tried to get th

Hi! Applied and pushed out. Aha, ok, that changs things. (I checked our trees but not stable). In such case, nothing needs to be done at the moment, and it is easier to wait till we merge that through

Hi! The patch looks okay to me. I'll test it and can apply it if it works okay. But I don't believe it is in our 5.10, so I'd like it to be submitted for 5.10, too. Or just tell me it is okay and I'll

Hi! gitlab seems to have some problems. 5.10.29-rc1 is not mirrored in gitlab: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y And I'm getting strange error while att

Hi! Every single test in -stable-rc series fails: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4.4.y https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/

Hi! New realtime trees should be available at kernel.org. They are based on -rt74 upstream version. Trees are available at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linu

Hi! I'm preparing new 4.19-rt release, and I see tests failing on zynqmp. https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/275281028 But they fail on old release, too, and IIRC 4.19 sim

Hi! New realtime trees should be available at kernel.org. Trees are available at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt https://git.kernel.org/pub/

Hi! Thank you, Renesas boards appear to work. But I still see random failures from test:x86_siemens_ipc227e_defconfig : Pipeline #273166880 has failed! Project: linux-cip ( https://gitlab.com/cip-proj

Hi! I'll not be able to make it to the irc meeting in time. I have reviewed patches queued for 5.10.24, and am still working on those. Best regards, Pavel

Hi! That's strange. ...because that particular change does not change any C code. But it touches Kconfig bits; can you check that CONFIG_SPI_CADENCE_QUADSPI is enabled in the "bad" configuration? Do y

Hi! Chris pointed out our master branch at git.kernel.org is rather old: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/refs/heads master CIP: Bump version suffix to -cip28 after Re

Hi! There was some discussion about futexes in 4.4 on irc. https://lore.kernel.org/stable/20210309030605.3295183-2-zhengyejian1@... I don't believe we need to do anything there. Peter Zijlstra

Hi! It is refered as "Type 1/4.0" and I'm not really sure what it means. 1/4 inch is 6.35mm, but document states it is 4.6mm. https://www.photoreview.com.au/tips/buying/unravelling-sensor-sizes/ expla

Hi! Well... test are okay, except that Renesas lab is offline so it was not really tested on Renesas targets. Anyway, I guess I'm okay with applying these if there are no other comments. Best regards,

Hi! I had some minor comments, but the series looks good; I guess we don't need to delay applying. Some of the patches are not in 5.10, so we'll need them in cip 5.10 branch, too? Let me do some testi

Hi! This needs to be normal comment style, and it needs to contain sentences. And it may be better to provide #ifdef for the alternate configuration. Best regards, Pavel

Hi! MHz? Make this usual comment style. ... ... I believe this should be "us" or "usec". This is not really english. That's really interesting piece of code. len is in bytes, but return value is in 32

Hi! /* * Sensor... would be the usual commment style. Best regards, Pavel

Hi! I assume it is 0.25 inch sensor? 1/4 inch or 0.25 inch would be understandable, but 1/4.0 is kind of strange. "V" should be uppercase in voltages. Best regards, Pavel