All of lore.kernel.org
 help / color / mirror / Atom feed
From: houdek.ryan@fex-emu.org
To: robdclark@gmail.com
Cc: abhinavk@codeaurora.org, airlied@linux.ie,
	dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
	kalyan_t@codeaurora.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, maxime@cerno.tech,
	miaoqinglang@huawei.com, robdclark@chromium.org, sean@poorly.run,
	swboyd@chromium.org, yaohongbo@huawei.com,
	Ryan Houdek <Houdek.Ryan@fex-emu.org>
Subject: Tested
Date: Sun,  9 May 2021 08:38:42 -0700	[thread overview]
Message-ID: <20210509153842.124974-1-Houdek.Ryan@fex-emu.org> (raw)
In-Reply-To: <20210508195641.397198-3-robdclark@gmail.com>

I have tested this on my end and it resolves the 120hz problem.

Tested-By: Ryan Houdek <Houdek.Ryan@fex-emu.org>

WARNING: multiple messages have this Message-ID (diff)
From: houdek.ryan@fex-emu.org
To: robdclark@gmail.com
Cc: robdclark@chromium.org, Ryan Houdek <Houdek.Ryan@fex-emu.org>,
	airlied@linux.ie, linux-arm-msm@vger.kernel.org,
	yaohongbo@huawei.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, swboyd@chromium.org,
	sean@poorly.run, miaoqinglang@huawei.com,
	abhinavk@codeaurora.org, kalyan_t@codeaurora.org,
	freedreno@lists.freedesktop.org, maxime@cerno.tech
Subject: Tested
Date: Sun,  9 May 2021 08:38:42 -0700	[thread overview]
Message-ID: <20210509153842.124974-1-Houdek.Ryan@fex-emu.org> (raw)
In-Reply-To: <20210508195641.397198-3-robdclark@gmail.com>

I have tested this on my end and it resolves the 120hz problem.

Tested-By: Ryan Houdek <Houdek.Ryan@fex-emu.org>

  reply	other threads:[~2021-05-09 15:39 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-08 19:56 [PATCH 0/2] drm: Fix atomic helper dirtyfb stalls Rob Clark
2021-05-08 19:56 ` Rob Clark
2021-05-08 19:56 ` [PATCH 1/2] drm: Fix " Rob Clark
2021-05-08 19:56   ` Rob Clark
2021-05-10 16:14   ` Daniel Vetter
2021-05-10 16:14     ` Daniel Vetter
2021-05-10 16:16     ` Daniel Vetter
2021-05-10 16:55     ` Rob Clark
2021-05-10 16:55       ` Rob Clark
2021-05-10 17:43       ` Daniel Vetter
2021-05-10 17:43         ` Daniel Vetter
2021-05-10 19:06         ` Rob Clark
2021-05-10 19:06           ` Rob Clark
2021-05-11 16:44           ` Daniel Vetter
2021-05-11 16:44             ` Daniel Vetter
2021-05-11 17:19             ` Rob Clark
2021-05-11 17:19               ` Rob Clark
2021-05-11 17:21               ` Daniel Vetter
2021-05-11 17:21                 ` Daniel Vetter
2021-05-11 17:42                 ` Rob Clark
2021-05-11 17:42                   ` Rob Clark
2021-05-11 17:50                   ` Daniel Vetter
2021-05-11 17:50                     ` Daniel Vetter
2021-05-12  8:23             ` Pekka Paalanen
2021-05-12  8:23               ` Pekka Paalanen
2021-05-12  8:44               ` Daniel Vetter
2021-05-12  8:44                 ` Daniel Vetter
2021-05-12  9:46                 ` Pekka Paalanen
2021-05-12  9:46                   ` Pekka Paalanen
2021-05-12 10:35                   ` Daniel Vetter
2021-05-12 10:35                     ` Daniel Vetter
2021-05-12 14:57               ` Rob Clark
2021-05-12 14:57                 ` Rob Clark
2021-05-14  7:54                 ` Pekka Paalanen
2021-05-14  7:54                   ` Pekka Paalanen
2021-05-14 14:43                   ` Rob Clark
2021-05-14 14:43                     ` Rob Clark
2021-05-08 19:56 ` [PATCH 2/2] drm/msm/dpu: Wire up needs_dirtyfb Rob Clark
2021-05-08 19:56   ` Rob Clark
2021-05-09 15:38   ` houdek.ryan [this message]
2021-05-09 15:38     ` Tested houdek.ryan
2021-05-10 15:26     ` Tested Alex Deucher
2021-05-10 15:26       ` Tested Alex Deucher
2021-05-09 16:28   ` [PATCH 2/2] drm/msm/dpu: Wire up needs_dirtyfb Rob Clark
2021-05-09 16:28     ` Rob Clark

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=20210509153842.124974-1-Houdek.Ryan@fex-emu.org \
    --to=houdek.ryan@fex-emu.org \
    --cc=abhinavk@codeaurora.org \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=kalyan_t@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime@cerno.tech \
    --cc=miaoqinglang@huawei.com \
    --cc=robdclark@chromium.org \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=swboyd@chromium.org \
    --cc=yaohongbo@huawei.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.