On 11/02/2026 11:08, Philipp Stanner wrote:
On Wed, 2026-01-28 at 11:07 +0000, Tvrtko Ursulin wrote:
** NOTE:
First three patches have been already reviewed and are conceptualy
independent. But as the code conflicts, I am including them while waiting
for
them to be merged via amd-next, and until they percolate back to drm-tip, in
order to avoid having to maintain two separate patch series.
So your intention with this v6 is just to get more reviews? What is the
purpose?
And since the plan is supposedly that the drm_sched maintainers take
it, when will they know that it's ready now?
Can we agree on delaying a v7 until all lights are green?
I am waiting on Christian to merge the first three patches via amd-next.
That is pending for a month now and in the meantime I did not want to
send this series and have someone tell me it does not apply. If by a
miracle someone actually went to try and give it a spin.
For the moment I don't think this is a problem for this series since
there are so many more patches still pending to review. And based on the
past experience you will not be merging it any time soon. As there are
no design conflicts between the two, the review can progress just fine
ignoring the first three patches.
For the future, I think the more canonical (and less confusing) way to
handle situations like this is not to include foreign patches into a
single-topic patch series, but to hint in the cover letter at the
situation and provide links: "Series is blocked by [1], [2]".
Again, like that it wouldn't build and no one would be able to test it.
For now just skip the first three and focus on the rest and hopefully by
v7 I will be able to drop those.
Regards,
Tvrtko
