Hi! https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022&month=5&day=12&hour=12&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248 I'm not sure if I'll be able to make it today. I wa

Hi! Ok, I created 5.10.109-based -rt release. I believe that would be rather "strange". I could do 4.19.240-rt108-cip72 based release, but I guess it will be better to wait for next 4.19-rt and do a m

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-5.10.y-cip-rt https://git.kernel.org/pub

Hi! In previous linux-4.4.y-cip-rebases, order of patches was: git log: [CIP patches] [Greg's stable tree] [Linus tree] With start of self-maintainance, we now have: git log: [-st patches] [CIP patche

Hi! I tried to do some testing, but it fails on two targets: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/522211501 And failed test says: https://lava.ciplatform.org/scheduler/job/6

Hi! There's oops during boot on socfpga: 4.19.240-cip72-00010-g0ffbb4b1066 -- https://lava.ciplatform.org/scheduler/job/669893 4.19.240-rc1-g5e5c9d690926 -- https://lava.ciplatform.org/scheduler/job/6

Hi! Aside from minor comments I sent, series looks good to me. I'm okay with series being merged. Thanks and best regards, Pavel

Hi! I just want to make sure: There are two frequencies, close to each other but not same. Is that okay? Best regards, Pavel

Hi! I guess there was two comments hidden in the quoted text. I'm not sure if you noticed them? Best regards, Pavel

Hi! AFAICT rz_ssi_dma_request() allocates resources and rz_ssi_release_dma_channels() is needed to free them if we fail. But in most failure paths below, that's not done, with one exception: Best rega

Hi! I would not mind . at the end of the sentence, to be consistent with the next paragraph, but that's really a nitpicking. Best regards, Pavel

Hi! It seems that zynqmp has problems: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/2336993733 Job #663506: Submitted 67Health: Unknown 68Device Type: zynqmp-zcu102 69Device: N

Hi! Not from me. My preferences are: best/1: permanently one hour earlier. 2: one hour earlier at least during DST. 3: current time. Best regards, Pavel

Hi! I see there are some changes: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y but it seems to say "authored 12 minutes ago". Hour ago it also said "authored 12 mi

Hi! ... After DST shift, 13 UTC is not really great time for me, either. 12 UTC would be better, 9 or 10 UTC would be even better. I don't propose shifting today's meeting, but should we talk about sh

Hi! 5.10.110-rc2 is out, and it would be good to test it, but somehow we are still at -rc1...? https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-5.10.y Does mirroring need to

Hi! ... I'd avoid using non-ASCII characters where possible. ... is not that much longer, and that symbol should really be -. Also comments should start with /* on separate line, but that's really det

Hi! Changelog says rename, but macro arguments are changed, so I want to make sure it was intended. Best regards, Pavel

Hi! I'd put space before */. ... I believe you need to undo effects of pm_runtime_resume_and_get() here and jump to out_pm_get. Best regards, Pavel

Hi! Thanks for the series. It passes testing and I do not see any problems that would prevent merge. I can merge it if there are no other comments. Best regards, Pavel