Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Tollet <jerome.tollet@gmail.com>
To: ankit.k.nautiyal@intel.com
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	ville.syrjala@linux.intel.com, arun.r.murthy@intel.com
Subject: Re: [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status
Date: Mon, 29 Jun 2026 08:17:05 +0200	[thread overview]
Message-ID: <20260629061705.55335-1-jerome.tollet@gmail.com> (raw)
In-Reply-To: <20260520022544.3097252-1-ankit.k.nautiyal@intel.com>

Hi Ankit,

I noticed commit b7d51d65e4f1 ("drm/i915/hdmi: Poll for 200 msec for
TMDS_Scrambler_Status") is in drm-intel-next since June 11.

Now that 7.2-rc1 is out and the patch does not seem to be in
for-linux-next/drm-next yet, could you let me know what the expected next
step is? Is there anything still needed from my side?

Thanks,
Jerome

  parent reply	other threads:[~2026-07-01 12:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  2:25 [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Ankit Nautiyal
2026-05-20  3:34 ` ✓ i915.CI.BAT: success for drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status (rev5) Patchwork
2026-05-21  7:25 ` ✓ i915.CI.Full: " Patchwork
2026-05-29  4:56 ` [RESEND] drm/i915/hdmi: Poll for 200 msec for TMDS_Scrambler_Status Jerome Tollet
2026-06-09  9:31   ` Jerome Tollet
2026-06-11  9:03 ` Nautiyal, Ankit K
2026-06-29  6:17 ` Jerome Tollet [this message]
     [not found] ` <20260727131445.28048-1-jerome.tollet@gmail.com>
2026-07-28 14:45   ` Nautiyal, Ankit K
     [not found] <20260113143107.1446909-1-ankit.k.nautiyal@intel.com>
2026-03-26  5:41 ` Jerome Tollet
2026-04-01 11:23   ` Ville Syrjälä
2026-04-01 12:26     ` Jerome Tollet
2026-05-05  5:37 ` Jerome Tollet
     [not found] <[email protected]>
2026-02-21  7:37 ` Jerome Tollet
  -- strict thread matches above, loose matches on Subject: below --
2026-01-28 10:12 Jérôme Tollet
2026-02-07  3:14 ` Jérôme Tollet
2026-02-14 16:17   ` Jérôme Tollet
2026-02-17  8:14     ` Nautiyal, Ankit K
2026-01-13 13:38 Ankit Nautiyal
2026-01-13 21:39 ` Ville Syrjälä
2026-01-21 12:56   ` Nautiyal, Ankit K
2026-02-19 15:45     ` Jerome Tollet
2026-02-27 13:16     ` Jerome Tollet
2026-02-27 14:03       ` Nautiyal, Ankit K

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=20260629061705.55335-1-jerome.tollet@gmail.com \
    --to=jerome.tollet@gmail.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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