All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>,
	"Jani Nikula" <jani.nikula@linux.intel.com>
Cc: <ville.syrjala@linux.intel.com>, <mitulkumar.ajitkumar.golani@intel.com>
Subject: Re: [PATCH 0/4] drm/i915/dp: Adaptive Sync SDP readback fixes
Date: Thu, 14 May 2026 17:21:21 +0530	[thread overview]
Message-ID: <c914295e-fa39-41ca-8159-c134301fd234@intel.com> (raw)
In-Reply-To: <20260511123218.1589830-1-ankit.k.nautiyal@intel.com>


On 5/11/2026 6:02 PM, Ankit Nautiyal wrote:
> This series is a spin-off from the original series [1] addressing AS SDP
> handling for Panel Replay and VRR.
>
> It fixes target_rr readback and improves overall Adaptive Sync SDP
> readback handling.
>
> Split out for easier review and merging.
>
> [1] https://patchwork.freedesktop.org/series/164512/

Hi Jani,

This series is reviewed and is ready to be merged, but one of the patch 
in the series depends on:
59e5e15fef9c ("drm/dp: Rename and relocate AS SDP payload field masks")

which was recently merged in drm-next, so it doesn’t apply cleanly on 
current drm-intel-next.

Would it be possible to get a backmerge from drm-next into 
drm-intel-next to bring this in?

In hindsight, I realize that in such cases where there is a dependency 
on drm patches,
I should have included them in a single series and asked for ack to 
merge via drm-intel-next.

I'll take care of this going forward.

Thanks & Regards,
Ankit



>
> Ankit Nautiyal (4):
>    drm/i915/dp: Fix readback for target_rr in Adaptive Sync SDP
>    drm/i915/dp: Use revision field of AS SDP data structure
>    drm/i915/dp: Set sdp_type in AS SDP unpack
>    drm/i915/dp: Include all relevant AS SDP fields in comparison
>
>   drivers/gpu/drm/i915/display/intel_display.c |  6 +++++-
>   drivers/gpu/drm/i915/display/intel_dp.c      | 10 +++++-----
>   2 files changed, 10 insertions(+), 6 deletions(-)
>

  parent reply	other threads:[~2026-05-14 11:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 12:32 [PATCH 0/4] drm/i915/dp: Adaptive Sync SDP readback fixes Ankit Nautiyal
2026-05-11 12:32 ` [PATCH 1/4] drm/i915/dp: Fix readback for target_rr in Adaptive Sync SDP Ankit Nautiyal
2026-05-11 12:32 ` [PATCH 2/4] drm/i915/dp: Use revision field of AS SDP data structure Ankit Nautiyal
2026-05-11 12:32 ` [PATCH 3/4] drm/i915/dp: Set sdp_type in AS SDP unpack Ankit Nautiyal
2026-05-11 13:07   ` Ville Syrjälä
2026-05-11 12:32 ` [PATCH 4/4] drm/i915/dp: Include all relevant AS SDP fields in comparison Ankit Nautiyal
2026-05-11 18:15 ` ✓ CI.KUnit: success for drm/i915/dp: Adaptive Sync SDP readback fixes Patchwork
2026-05-11 19:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-11 19:13 ` ✓ i915.CI.BAT: " Patchwork
2026-05-11 20:53 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-12  1:26 ` ✓ i915.CI.Full: " Patchwork
2026-05-14 11:51 ` Nautiyal, Ankit K [this message]
2026-05-15 10:55   ` [PATCH 0/4] " Jani Nikula
2026-05-15 11:49     ` Rodrigo Vivi
2026-05-16  6:27       ` 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=c914295e-fa39-41ca-8159-c134301fd234@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=mitulkumar.ajitkumar.golani@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.