Re: Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch

[Jani Nikula <jani.nikula@linux.intel.com>]

On Wed, 29 Jul 2026, Jerome Tollet <jerome.tollet@gmail.com> wrote:
> Hi Jani,
>
> I would like to better understand the i915 patch flow, rather than question
> the decision itself.
>
> The commit b7d51d65e4f1 ("drm/i915/hdmi: Poll for 200 msec for
> TMDS_Scrambler_Status") was pushed to drm-intel-next on June 11. It was then
> included in the July 2 drm-intel-next pull, described as the first feature
> pull towards v7.3.
>
> However, it was not included in the drm-intel-next-fixes pulls for v7.2,
> including the June 25 pull, and it is consequently not present in v7.2-rc5.
>
> Could you please explain how the decision is made to route a patch to
> drm-intel-next versus drm-intel-next-fixes? In this particular case, was
> there a technical or review reason why the patch was not considered for the
> v7.2 fixes pull, or was it mainly a timing/queueing decision?
>
> I am asking to understand the process for future contributions.

All i915 patches get applied to drm-intel-next first, and fixes are
cherry-picked to drm-intel-fixes/drm-intel-next-fixes based on Fixes:
and Cc: stable trailers. In this case, the patch had neither, and none
were added while applying the patch.

It can still be cherry-picked for drm-intel-fixes if necessary.


BR,
Jani.

-- 
Jani Nikula, Intel