On Wed, Jul 06, 2022 at 05:07:12PM +0200, Krzysztof Kozlowski wrote: > On 06/07/2022 12:20, Christian Marangi wrote: > > On Wed, Jul 06, 2022 at 09:44:04AM +0200, Krzysztof Kozlowski wrote: > >> On 05/07/2022 22:28, Christian Marangi wrote: > >>> Fix dtbs_check warning for new rpmcc Documentation changes and add the > >>> required clocks. > >> > >> There is no warning in the kernel, right? So the commit is not correct. > >> > > > > Oh ok, the warning is generated by the new Documentation. > > Patches, especially DTS, might go via different trees, so the moment DTS > is applied there might be no such warning. > I'm still confused about this topic... With this kind of change, I notice I sent Documentation change and then rob bot complain about dtbs_check having warning... So the correct way is to send Documentation change and fix dtbs_check warning in the same commit OR keep what I'm doing with sending Documentation changes and fix DTS in a separate commit? I assume separate patch was the way to go but now I'm not sure anymore... > Best regards, > Krzysztof -- Ansuel
