Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jerome Tollet <jerome.tollet@gmail.com>
Cc: <jani.nikula@linux.intel.com>, <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>
Subject: Re: Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch
Date: Thu, 30 Jul 2026 10:13:32 -0400	[thread overview]
Message-ID: <amtcDFjbZ4w_OeNG@intel.com> (raw)
In-Reply-To: <20260730033607.17136-1-jerome.tollet@gmail.com>

On Thu, Jul 30, 2026 at 05:36:07AM +0200, Jerome Tollet wrote:
> Hi Jani,
> 
> Thanks, this clarifies the process.
> 
> I understand that the patch was applied to drm-intel-next first, but since it
> had neither a Fixes: nor a Cc: stable@vger.kernel.org trailer, it was not
> selected for drm-intel-fixes.
> 
> Since the patch fixes 4K@60Hz failures on some HDMI 2.0 sinks, and has passed
> CI and review, would you consider it appropriate to cherry-pick it into
> drm-intel-fixes for Linux 7.2, or should it remain targeted at Linux 7.3?

I will pick this up and send towards the 7.2

Do you agree that a proper fixes tag for this patch should be:

Fixes: 15953637886d ("drm/i915: enable scrambling")

?

If so I will manually add it while picking up for fixes.

Thanks,
Rodrigo.

> 
> I am happy to provide any additional testing or information if needed.
> 
> Thanks,
> Jerome

      parent reply	other threads:[~2026-07-30 14:13 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 ` Question about drm-intel-next vs drm-intel-next-fixes for HDMI scrambling patch Jani Nikula
     [not found] ` <20260730033607.17136-1-jerome.tollet@gmail.com>
2026-07-30 14:13   ` Rodrigo Vivi [this message]

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=amtcDFjbZ4w_OeNG@intel.com \
    --to=rodrigo.vivi@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=jani.nikula@linux.intel.com \
    --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