From: Jerome Tollet <jerome.tollet@gmail.com>
To: jani.nikula@linux.intel.com
Cc: ankit.k.nautiyal@intel.com, ville.syrjala@linux.intel.com,
arun.r.murthy@intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Jerome Tollet <jerome.tollet@gmail.com>
Subject: Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch
Date: Wed, 29 Jul 2026 18:16:06 +0200 [thread overview]
Message-ID: <20260729161606.81668-1-jerome.tollet@gmail.com> (raw)
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
next reply other threads:[~2026-07-29 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 16:16 Jerome Tollet [this message]
2026-07-29 21:23 ` Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch Jani Nikula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260729161606.81668-1-jerome.tollet@gmail.com \
--to=jerome.tollet@gmail.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ville.syrjala@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.