On 11/02/2026 11:07, Erikas Bitovtas wrote: > > > On 2/11/26 8:49 AM, Krzysztof Kozlowski wrote: >> >> There was CM36686 v1 and v2, so I do not understand versioning here. >> Also, lack of any changelog. >> >> And how is it supposed to work for us? Try yourself: >> >> $ b4 diff [email protected] >> Could not find lower series to compare against.
Look here. >> >> Please implement previous feedback. >> >> Best regards, >> Krzysztof >> > > Since I am making changes to the existing driver instead of creating a new > one, > I introduced a new patch series. As I mentioned in the cover letter, cm36686 > is > fully compatible with vcnl4040, so instead of creating a new binding, I > create a > fallback compatible for the device. I probably should have named this patch > series something else. That's fine, but that's v3 of previous patches. Your work was to add CM36686 support. How you do it, evolves, but patchset/work is one continuous work. When you rework approach next time, you also start from v1? And then you go back to previous solution of new driver it will jump from v1 to v3? > As for the previous feedback, I added the subject prefix and removed the > redundant phrasing. And how do I know it if there is no changelog with list of changes? Look how many patches is here: https://lore.kernel.org/linux-devicetree/ Best regards, Krzysztof
