All of lore.kernel.org
 help / color / mirror / Atom feed
* Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch
@ 2026-07-29 16:16 Jerome Tollet
  2026-07-29 21:23 ` Jani Nikula
  2026-07-30  3:36 ` Jerome Tollet
  0 siblings, 2 replies; 5+ messages in thread
From: Jerome Tollet @ 2026-07-29 16:16 UTC (permalink / raw)
  To: jani.nikula
  Cc: ankit.k.nautiyal, ville.syrjala, arun.r.murthy, intel-gfx,
	dri-devel, Jerome Tollet

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.

Thanks,
Jerome

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2026-07-30 16:31 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-29 16:16 Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch Jerome Tollet
2026-07-29 21:23 ` Jani Nikula
2026-07-30  3:36 ` Jerome Tollet
2026-07-30 14:13   ` Rodrigo Vivi
2026-07-30 16:31   ` Jerome Tollet

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.