From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: "Qu, Jim" <Jim.Qu-5C7GfCeVMHo@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: 答复: 答复: [PATCH] sync amdgpu scanout update event before mode setting
Date: Wed, 18 Apr 2018 11:54:27 +0200 [thread overview]
Message-ID: <13cab810-0bb7-b6fc-3e8a-7b1f0835b303@daenzer.net> (raw)
In-Reply-To: <DM3PR12MB087312990AC89B251353463299B60-4hRkV8tDpBiYEITDcfEJ8AdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
On 2018-04-18 11:44 AM, Qu, Jim wrote:
> Yeah, I realize that it should use || . I will check it again with your
> modification.
I've verified that it fixes the crash.
> and then push it immediately. The issue has delayed a long time.
Really? I haven't seen anything about this before you posted your patch
yesterday. (I wonder if
https://bugs.freedesktop.org/show_bug.cgi?id=105736 might be the same
issue, but it's not clear yet)
> May I get your RB?
I'd prefer pushing it myself.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-04-18 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 11:11 [PATCH] sync amdgpu scanout update event before mode setting Jim Qu
[not found] ` <1523963476-17769-1-git-send-email-Jim.Qu-5C7GfCeVMHo@public.gmane.org>
2018-04-18 2:22 ` 答复: " Qu, Jim
2018-04-18 8:55 ` Michel Dänzer
[not found] ` <6c324f68-e642-fdc9-3fe7-86f956f23a9e-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-04-18 9:00 ` 答复: " Qu, Jim
[not found] ` <DM3PR12MB087344C174A5B88C5D55AFB899B60-4hRkV8tDpBiYEITDcfEJ8AdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-04-18 9:12 ` Qu, Jim
[not found] ` <DM3PR12MB087326EF8F4A655E0DBE16FF99B60-4hRkV8tDpBiYEITDcfEJ8AdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-04-18 9:29 ` Michel Dänzer
[not found] ` <558e5cc3-2ff1-5116-fb67-2a1ce927cc52-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-04-18 9:44 ` 答复: " Qu, Jim
[not found] ` <DM3PR12MB087312990AC89B251353463299B60-4hRkV8tDpBiYEITDcfEJ8AdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-04-18 9:54 ` Michel Dänzer [this message]
[not found] ` <13cab810-0bb7-b6fc-3e8a-7b1f0835b303-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-04-18 9:57 ` 答复: " Qu, Jim
[not found] ` <DM3PR12MB0873E5ADB6D637077BEADAEB99B60-4hRkV8tDpBiYEITDcfEJ8AdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-04-18 10:12 ` Michel Dänzer
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=13cab810-0bb7-b6fc-3e8a-7b1f0835b303@daenzer.net \
--to=michel-otuistvhuppr7s880joybq@public.gmane.org \
--cc=Jim.Qu-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.