07:05 <krzk> bryanodonoghue: Did you apply qcs8300 camss? "[PATCH v3 1/7] media: dt-bindings: Add qcom,qcs8300-camss compatible" and the rest?

07:05 <krzk> I cannot find it in the next, but I want to be sure

08:15 <bryanodonoghue> 634a2958fae30 - media: dt-bindings: Add qcom,qcs8300-camss compatible

08:15 <bryanodonoghue> media-committers/next

08:15 <bryanodonoghue> media-committersgit@ssh.gitlab.freedesktop.org:linux-media/media-committers.git (fetch)

08:16 <bryanodonoghue> I don't think it will hit -next until -rc6

08:29 <krzk> bryanodonoghue: what do you mean "it will not hit next"? if you took the patch, it must be in next

08:30 <krzk> So this patchset is the exact example from my talk on LPC 23 - nothing on mailing lists that it was applied, nothing in the next, so no one except you knows it was applied. :/

08:30 <krzk> Anyway if it is not in the next, then I guess because you can freely change it, so please drop it - it is wrong, buggy/incomplete.

08:31 <bryanodonoghue> has your RB what's incomplete ?

08:31 <krzk> Rb was complete, but qcom now wrote that patch is wrong

08:32 <bryanodonoghue> hmm ok let me look at the thread on email

08:34 <bryanodonoghue> ahh the supplies are missing

11:42 <bryanodonoghue> krzk so I can pick up 20250909114241.840842-5-quic_vikramsa@quicinc.com and fix the commit log

11:42 <bryanodonoghue> that should resolve the problem before it hits -next

12:26 <krzk> So none of media patches are ever in the next before they hit your upstream maintainer... that's so broken media process (not your fault!). Ugh :(