The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Cooper Morgan <ext-github@cwooper.dev>
To: Wayne.Lin@amd.com
Cc: oss@oysterdaisuki.com, harry.wentland@amd.com,
	alexander.deucher@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: Tue, 17 Nov 2026 10:34:40 -0800	[thread overview]
Message-ID: <20261117183440.552477-1-ext-github@cwooper.dev> (raw)
In-Reply-To: <20261113010529.11514-1-ext-github@cwooper.dev>

Hi Wayne,

Thanks for picking these up! I noticed they went into
amd-staging-drm-next from v1 (bedad38a7ddf and ae60ec4dcfc4), not this
v2.

The code is the same, but v2 has oystersuki's Tested-by on both patches
and Suggested-by on patch 1. They tested the series on the 280Hz LG from
issue 5988 and asked to be credited, so I'd like that to make it in. v2
also drops a line from the patch 1 message about my EDID test that
turned out to be wrong.

If there's still time before it goes out in a pull, could you swap in
v2 or add the tags? If it's already set, no worries.

Thanks,
Cooper

      parent reply	other threads:[~2026-11-17 18:35 UTC|newest]

Thread overview: 4+ 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 ` Cooper Morgan [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=20261117183440.552477-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=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