From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org>
To: "Christian König"
<deathsimple-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>,
"Alex Deucher"
<alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: upsteam find bo api
Date: Mon, 19 Jun 2017 10:23:02 +0800 [thread overview]
Message-ID: <59473586.3010206@amd.com> (raw)
In-Reply-To: <431202a9-c20d-fc67-9e70-26dfb67a3792-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2202 bytes --]
On 2017年06月17日 18:09, Christian König wrote:
> The patch should still work on amd-staging-4.11, but drm-next has seen
> some changes on how the handles are stored for dma-buf.
>
> This can potentially break the implementation and I think we need to
> adapt before pushing it upstream, but I'm not 100% sure.
Do you mean the patch needs to wait for next kernel promotion? 4.12? 4.13?
Regards,
David Zhou
>
> Christian.
>
> Am 16.06.2017 um 22:35 schrieb Alex Deucher:
>> The patches look good to me. Christian what did you have in mind?
>> Acked-by: Alex Deucher <alexander.deucher-5C7GfCeVMHo@public.gmane.org
>> <mailto:alexander.deucher-5C7GfCeVMHo@public.gmane.org>>
>>
>> Alex
>>
>> On Fri, Jun 16, 2017 at 4:08 AM, zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org
>> <mailto:david1.zhou-5C7GfCeVMHo@public.gmane.org>> wrote:
>>
>> ping...?
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject: upsteam find bo api
>> Date: Wed, 14 Jun 2017 18:16:24 +0800
>> From: zhoucm1 <david1.zhou-5C7GfCeVMHo@public.gmane.org> <mailto:david1.zhou-5C7GfCeVMHo@public.gmane.org>
>> To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
>> <mailto:amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
>>
>>
>>
>> Hi all,
>>
>> Since patches are one feature, and contain kernel and libdrm, I attached
>> them not by send-mail. Hope not inconvenience.
>>
>> 0001-drm-amdgpu-return-bo-itself-if-userptr-is-cpu-addr-o.patch is
>> kernel patch.
>> Other three is libdrm patches including unit test.
>>
>> please review.
>>
>> Regards,
>> David Zhou
>>
>>
>>
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org <mailto:amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>> <https://lists.freedesktop.org/mailman/listinfo/amd-gfx>
>>
>>
>>
>>
>> _______________________________________________
>> amd-gfx mailing list
>> amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
>> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
>
>
[-- Attachment #1.2: Type: text/html, Size: 6811 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2017-06-19 2:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 20:12 [PATCH] drm/amdgpu/gfx9: support the amdgpu.disable_cu option Nicolai Hähnle
[not found] ` <20170613201205.21138-1-nhaehnle-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-14 10:16 ` upsteam find bo api zhoucm1
[not found] ` <59410CF8.9080409-5C7GfCeVMHo@public.gmane.org>
2017-06-16 8:08 ` Fwd: " zhoucm1
[not found] ` <59439208.10100-5C7GfCeVMHo@public.gmane.org>
2017-06-16 8:47 ` He, Roger
[not found] ` <BN6PR1201MB01146CE5D18B1D3AB252A235FDC10-6iU6OBHu2P8MH+E/uqw63WrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-06-16 11:18 ` 回复: " Zhou, David(ChunMing)
[not found] ` <MWHPR1201MB02069C5081958567754E38CCB4C10-3iK1xFAIwjrUF/YbdlDdgWrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-06-19 1:52 ` He, Roger
2017-06-16 15:37 ` Alex Deucher
2017-06-16 10:51 ` Emil Velikov
2017-06-16 20:35 ` Alex Deucher
[not found] ` <CADnq5_NY8pZr6JbD8GrUQatiFGz6J1dU9ug2TiFiyN+6kxozeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-17 10:09 ` Christian König
[not found] ` <431202a9-c20d-fc67-9e70-26dfb67a3792-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-06-19 2:23 ` zhoucm1 [this message]
[not found] ` <59473586.3010206-5C7GfCeVMHo@public.gmane.org>
2017-06-19 8:50 ` Christian König
[not found] ` <6ce7c117-99d8-36b5-31cf-cc8689ed8a38-ANTagKRnAhcb1SvskN2V4Q@public.gmane.org>
2017-06-19 22:35 ` Deucher, Alexander
2017-06-14 15:05 ` [PATCH] drm/amdgpu/gfx9: support the amdgpu.disable_cu option Deucher, Alexander
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=59473586.3010206@amd.com \
--to=david1.zhou-5c7gfcevmho@public.gmane.org \
--cc=alexdeucher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=deathsimple-ANTagKRnAhcb1SvskN2V4Q@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.