From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jerome Tollet <jerome.tollet@gmail.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: Re: Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch
Date: Thu, 30 Jul 2026 00:23:22 +0300 [thread overview]
Message-ID: <6b812bfdbcfcf3a090b22413db3ef57d75bc2058@intel.com> (raw)
In-Reply-To: <20260729161606.81668-1-jerome.tollet@gmail.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
next parent reply other threads:[~2026-07-29 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260729161606.81668-1-jerome.tollet@gmail.com>
2026-07-29 21:23 ` Jani Nikula [this message]
[not found] ` <20260730033607.17136-1-jerome.tollet@gmail.com>
2026-07-30 14:13 ` Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch Rodrigo Vivi
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=6b812bfdbcfcf3a090b22413db3ef57d75bc2058@intel.com \
--to=jani.nikula@linux.intel.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=jerome.tollet@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox