From: Chunming Zhou <zhoucm1@amd.com>
To: Daniel Vetter <daniel@ffwll.ch>,
"Zhou, David(ChunMing)" <David1.Zhou@amd.com>
Cc: "Michel D鋘zer" <michel@daenzer.net>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>, "Zhu, Seth" <Seth.Zhu@amd.com>
Subject: Re: [PATCH libdrm] drm: fix return value
Date: Wed, 17 Jan 2018 16:53:17 +0800 [thread overview]
Message-ID: <bd041e55-221d-70f9-c6ac-8838bf8a91aa@amd.com> (raw)
In-Reply-To: <20180117082114.GD2759@phenom.ffwll.local>
On 2018年01月17日 16:21, Daniel Vetter wrote:
> On Tue, Jan 16, 2018 at 02:01:40PM +0000, Zhou, David(ChunMing) wrote:
>> Can your guys help me push it and last vamgr patches to upstream?
>> My new count request for libdrm still is under pending.
> Or hand out commmit rights? That's easier long-term imo ...
That's not true, we need to track the commit for driver release, if we
have no permission to push it, we often need to check the patch status
to see if it's already in there.
Are you admin for count request? if you are, and approve my count
request, I greatly appreciate your approval.
Regards,
David Zhou
> -Daniel
>
>> Thanks,
>> David Zhou
>>
>>
>> 发自坚果 Pro
>>
>> Christian K鰊ig <ckoenig.leichtzumerken@gmail.com> 于 2018年1月16日 下午4:56写道:
>>
>> Apart from that a good catch and Reviewed-by: Christian König
>> <christian.koenig@amd.com>.
>>
>> Regards,
>> Christian.
>>
>> Am 16.01.2018 um 09:49 schrieb Michel Dänzer:
>>> Moving from the amd-gfx list to dri-devel, since this isn't amdgpu specific.
>>>
>>>
>>> On 2018-01-16 03:54 AM, Chunming Zhou wrote:
>>>> otherwise -ETIME is missed.
>>>>
>>>> Change-Id: Ic5580a74d8027cc468c6135f8cf2f81817993423
>>>> Signed-off-by: Chunming Zhou <david1.zhou@amd.com>
>>>> ---
>>>> xf86drm.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/xf86drm.c b/xf86drm.c
>>>> index 8a327170..3881bd9f 100644
>>>> --- a/xf86drm.c
>>>> +++ b/xf86drm.c
>>>> @@ -4241,7 +4241,7 @@ int drmSyncobjWait(int fd, uint32_t *handles, unsigned num_handles,
>>>>
>>>> ret = drmIoctl(fd, DRM_IOCTL_SYNCOBJ_WAIT, &args);
>>>> if (ret < 0)
>>>> - return ret;
>>>> + return -errno;
>>>>
>>>> if (first_signaled)
>>>> *first_signaled = args.first_signaled;
>>>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-17 8:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180116025401.18906-1-david1.zhou@amd.com>
2018-01-16 8:49 ` [PATCH libdrm] drm: fix return value Michel Dänzer
2018-01-16 8:56 ` Christian König
2018-01-16 14:01 ` Zhou, David(ChunMing)
2018-01-17 8:21 ` Daniel Vetter
2018-01-17 8:53 ` Chunming Zhou [this message]
2018-01-17 9:24 ` Christian König
2018-01-17 9:26 ` Chunming Zhou
2018-01-17 9:31 ` Daniel Vetter
2018-01-31 2:49 ` Chunming Zhou
2018-01-31 8:09 ` Daniel Vetter
2018-01-16 2:54 Chunming Zhou
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=bd041e55-221d-70f9-c6ac-8838bf8a91aa@amd.com \
--to=zhoucm1@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=David1.Zhou@amd.com \
--cc=Seth.Zhu@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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