On 08/07/2024 09:13, Aiqun Yu (Maria) wrote: > > > On 7/8/2024 2:07 PM, Krzysztof Kozlowski wrote: >> On 08/07/2024 06:45, Aiqun Yu (Maria) wrote: >>> >>> >>> On 7/3/2024 5:33 PM, Krzysztof Kozlowski wrote: >>>> On 03/07/2024 11:21, Tengfei Fan wrote: >>>>>>> - items: >>>>>>> - enum: >>>>>>> + - qcom,qcs9100-ride >>>>>>> - qcom,sa8775p-ride >>>>>>> + - const: qcom,qcs9100 >>>>>> >>>>>> This changes existing compatible for sa8775p without any explanation in >>>>>> commit msg. >>>>>> >>>>>> Best regards, >>>>>> Krzysztof >>>>>> >>>>> >>>>> In the next verion patch series, I will provide relevant explanatory >>>>> information in this patch commit message. >>>> >>>> TBH, I cannot think of any reasonable explanation for this, especially >>>> considering rest of the patchset which does not fix resulting dtbs_check >>>> warning. >>> >>> The existing compatible "sa8775p" warning can only be addressed When >>> @Nikunj's "sa8775p" changes merged. >>> >>> Let me know if you have other suggestions for this. >> >> I don't have, because I don't understand why do you want/need to change >> existing board compatible. > > We can left the current existing sa8775p board compatible as it is. And > have a brand new qcs9100 and qcs9100-board item for current non-scmi > resources compatible. > > Will that be more reasonable from your end? Yes, this is what I would expect. If you choose any other way - just like I wrote - you need to explain why you are doing this. Best regards, Krzysztof
