From: Alex Deucher <alexdeucher@gmail.com>
To: houdek.ryan@fex-emu.org
Cc: Rob Clark <robdclark@gmail.com>,
robdclark@chromium.org, Dave Airlie <airlied@linux.ie>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
yaohongbo@huawei.com, LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
swboyd@chromium.org, Sean Paul <sean@poorly.run>,
Qinglang Miao <miaoqinglang@huawei.com>,
abhinavk@codeaurora.org, kalyan_t@codeaurora.org,
freedreno <freedreno@lists.freedesktop.org>,
Maxime Ripard <maxime@cerno.tech>
Subject: Re: Tested
Date: Mon, 10 May 2021 11:26:08 -0400 [thread overview]
Message-ID: <CADnq5_OYRP5EE3GOdY6HyTcJuLxXw5V7X9fTTw+QMrKs6cjcvw@mail.gmail.com> (raw)
In-Reply-To: <20210509153842.124974-1-Houdek.Ryan@fex-emu.org>
Sorry, what patch are you referring to?
Alex
On Mon, May 10, 2021 at 4:04 AM <houdek.ryan@fex-emu.org> wrote:
>
> 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: Alex Deucher <alexdeucher@gmail.com>
To: houdek.ryan@fex-emu.org
Cc: robdclark@chromium.org,
freedreno <freedreno@lists.freedesktop.org>,
Dave Airlie <airlied@linux.ie>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
yaohongbo@huawei.com, LKML <linux-kernel@vger.kernel.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
swboyd@chromium.org, Qinglang Miao <miaoqinglang@huawei.com>,
kalyan_t@codeaurora.org, abhinavk@codeaurora.org,
Sean Paul <sean@poorly.run>, Maxime Ripard <maxime@cerno.tech>
Subject: Re: Tested
Date: Mon, 10 May 2021 11:26:08 -0400 [thread overview]
Message-ID: <CADnq5_OYRP5EE3GOdY6HyTcJuLxXw5V7X9fTTw+QMrKs6cjcvw@mail.gmail.com> (raw)
In-Reply-To: <20210509153842.124974-1-Houdek.Ryan@fex-emu.org>
Sorry, what patch are you referring to?
Alex
On Mon, May 10, 2021 at 4:04 AM <houdek.ryan@fex-emu.org> wrote:
>
> I have tested this on my end and it resolves the 120hz problem.
>
> Tested-By: Ryan Houdek <Houdek.Ryan@fex-emu.org>
next prev parent reply other threads:[~2021-05-10 15:31 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 ` Tested houdek.ryan
2021-05-09 15:38 ` Tested houdek.ryan
2021-05-10 15:26 ` Alex Deucher [this message]
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=CADnq5_OYRP5EE3GOdY6HyTcJuLxXw5V7X9fTTw+QMrKs6cjcvw@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=houdek.ryan@fex-emu.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.