On 02-11-2026 14:23, Krzysztof Kozlowski wrote: > On 01/11/2026 23:21, Ekansh Gupta wrote: >> drivers/accel/qda/qda_soc.c | 66 ++ >> drivers/accel/qda/qda_soc.h | 61 ++ >> drivers/misc/Kconfig | 1 + >> include/uapi/drm/qda_accel.h | 282 +++++++ >> 33 files changed, 5877 insertions(+), 1 deletion(-) >> --- >> base-commit: 7649ba73f9e7e1e04d0b46213e39c79ae09dd55c >> change-id: 20261102-v4-e8feb321263f > > What is happening here? How are we supposed to work with this? > > v1: 20260223-qda-firstpost-4ab05249e2cc > v2: 20260519-qda-series-78c2bf0ed78b > v2 again: 20260817-qda-v2-78e2d1f10529 > > And now completely different one? > > This makes the change id completely unusable. b4 diff obviously does not > work. Any tracking of this does not work. > > NAK, really, I already complained internally months ago about such > practice, so apparently not enough. > > Best regards, > Krzysztof
Sorry about this. I lost the original b4 branch and re-enrolled the series for v4, which generated a new change-id. I should have carried the existing one over. I have restored the v3 change-id (20260817-qda-v2-78e2d1f10529) on the branch, and it will stay fixed for all future revisions of this series. v5 will use it. Note that v4 is a substantial rework of v3 (the custom bus and iommu patches are gone, the legacy shim is new and the series is reordered), so a range-diff against v3 would be of limited use; the "Changes in v4" section in the cover letter lists what changed and why. //Ekansh
