From: Harry Wentland <harry.wentland@amd.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alex Deucher <alexdeucher@gmail.com>, Jun Lei <Jun.Lei@amd.com>,
Mustapha Ghaddar <mustapha.ghaddar@amd.com>,
Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
meenakshikumar somasundaram <meenakshikumar.somasundaram@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Dave Airlie <airlied@gmail.com>,
"Koenig, Christian" <christian.koenig@amd.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [git pull] drm for 5.17-rc1 (pre-merge window pull)
Date: Wed, 12 Jan 2022 10:36:53 -0500 [thread overview]
Message-ID: <4dace73c-c37b-2eab-c9f3-49349ef7c0ee@amd.com> (raw)
In-Reply-To: <CAHk-=whZW+Cy++vucKQd6Lrj7B1bhd1-pKkgV8xxPJr35Dh2UA@mail.gmail.com>
On 2022-01-11 15:51, Linus Torvalds wrote:
> On Tue, Jan 11, 2022 at 7:38 AM Harry Wentland <harry.wentland@amd.com> wrote:
>>
>> Attached is a v2 of the buggy patch that should get this right.
>> If you have a chance to try it out let us know
>
> I can confirm that I do not see the horribly flickering behavior with
> this patch.
Thanks for testing it. The patch is up for review on the amd-gfx
mailing list.
Harry
prev parent reply other threads:[~2022-01-12 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 6:12 Dave Airlie
2022-01-07 10:37 ` Christian König
2022-01-10 21:10 ` Linus Torvalds
2022-01-10 21:27 ` pr-tracker-bot
2022-01-10 21:30 ` Linus Torvalds
2022-01-10 22:04 ` Daniel Vetter
2022-01-10 22:13 ` Alex Deucher
2022-01-11 1:04 ` Linus Torvalds
2022-01-11 1:11 ` Alex Deucher
2022-01-11 1:21 ` Linus Torvalds
2022-01-11 1:28 ` Linus Torvalds
2022-01-11 2:22 ` Linus Torvalds
2022-01-11 2:44 ` Linus Torvalds
2022-01-11 2:52 ` Linus Torvalds
2022-01-11 15:08 ` Alex Deucher
2022-01-11 15:38 ` Harry Wentland
2022-01-11 20:51 ` Linus Torvalds
2022-01-12 15:36 ` Harry Wentland [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=4dace73c-c37b-2eab-c9f3-49349ef7c0ee@amd.com \
--to=harry.wentland@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Jun.Lei@amd.com \
--cc=airlied@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.wheeler@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meenakshikumar.somasundaram@amd.com \
--cc=mustapha.ghaddar@amd.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®