The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Cooper Morgan <ext-github@cwooper.dev>
To: Alex Deucher <alexander.deucher@amd.com>
Cc: erenozen@protonmail.com, Wayne.Lin@amd.com,
	oss@oysterdaisuki.com, harry.wentland@amd.com,
	amd-gfx@lists.freedesktop.org, sunpeng.li@amd.com,
	siqueira@igalia.com, christian.koenig@amd.com, airlied@gmail.com,
	simona@ffwll.ch, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] drm/amd/display: Fix FreeSync infopacket refresh rates above 255 Hz
Date: Wed, 18 Nov 2026 17:41:15 -0800	[thread overview]
Message-ID: <20261119014116.3632450-1-ext-github@cwooper.dev> (raw)
In-Reply-To: <HftAWPKURVjBtK_2BmUiLXOb8ghZxaEzAJSg0tlsmy5L3ckJyDWc6g65vrsVGdA3ZcytB6mPuyxaQbsPawfOZmdC1dyAo4lCbaK3Tj7Tm-U=@protonmail.com>

Hi Alex,

The copies in drm-fixes-7.4 and drm-next have the same problem Eren
found. Patch 2 there (6a9d5e2f, e1c26823) is missing the
amdgpu_dm_connector.c hunk, and its connector test went with it, so
nothing fails on those branches.

Could you swap in v2 before the fixes pull goes out? It has the hunk,
plus oystersuki's Tested-by and Suggested-by tags.

Thanks,
Cooper

  reply	other threads:[~2026-11-19  1:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13  1:05 [PATCH v2 0/2] drm/amd/display: Fix FreeSync infopacket refresh rates above 255 Hz Cooper Morgan
2026-11-13  1:05 ` [PATCH v2 1/2] drm/amd/display: Saturate refresh rates in v1/v2 FreeSync infopackets Cooper Morgan
2026-11-13  1:05 ` [PATCH v2 2/2] drm/amd/display: Use FreeSync v3 infopacket for sinks above 255 Hz Cooper Morgan
2026-11-17 18:34 ` [PATCH v2 0/2] drm/amd/display: Fix FreeSync infopacket refresh rates " Cooper Morgan
2026-11-18 12:46   ` Eren Özen
2026-11-19  1:41     ` Cooper Morgan [this message]
2026-11-19  3:05     ` Wayne Lin

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=20261119014116.3632450-1-ext-github@cwooper.dev \
    --to=ext-github@cwooper.dev \
    --cc=Wayne.Lin@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=erenozen@protonmail.com \
    --cc=harry.wentland@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oss@oysterdaisuki.com \
    --cc=simona@ffwll.ch \
    --cc=siqueira@igalia.com \
    --cc=sunpeng.li@amd.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