From: "Zhang, Jerry (Junwei)" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>,
"Christian König"
<ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH libdrm 1/6] amdgpu: always add all BOs to lockup table
Date: Fri, 3 Aug 2018 11:13:31 +0800 [thread overview]
Message-ID: <5B63C85B.6030103@amd.com> (raw)
In-Reply-To: <2ede6f59-a1e6-fe9e-396f-2cc961db6df5-otUistvHUpPR7s880joybQ@public.gmane.org>
On 08/02/2018 10:55 PM, Michel Dänzer wrote:
> On 2018-08-02 04:04 PM, Christian König wrote:
>> This way we can always find a BO structure by its handle.
>>
>> Signed-off-by: Christian König <christian.koenig@amd.com>
>
> Typo in the shortlog: should be "lookup" instead of "lockup".
>
> Also, this patch should really be after patch 4.
>
>
>> @@ -240,14 +237,11 @@ int amdgpu_bo_export(amdgpu_bo_handle bo,
>> return 0;
>>
>> case amdgpu_bo_handle_type_kms:
>> - amdgpu_add_handle_to_table(bo);
>> - /* fall through */
>> case amdgpu_bo_handle_type_kms_noimport:
>> *shared_handle = bo->handle;
>> return 0;
>
> This is a bit unfortunate, amdgpu_bo_handle_type_kms_noimport only just
> landed this week for the 2.4.93 release, now it'll already be useless
> noise... A bit more coordination would have been nice. :)
BTW, there is a schedule for that release?
I mean if amdgpu_bo_handle_type_kms_noimport is merged in the release at last minute.
Generally we may wait for some verification or process for a release.
if the func has to go through a verification/process, that maybe not happen in a week.
Jerry
>
>
> Anyway, with the typo in patch 3 fixed, patches 2 & 4-6 are
>
> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
>
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-08-03 3:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 14:04 [PATCH libdrm 1/6] amdgpu: always add all BOs to lockup table Christian König
[not found] ` <20180802140452.23894-1-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-08-02 14:04 ` [PATCH libdrm 2/6] amdgpu: stop using the hash table for fd_tab Christian König
2018-08-02 14:04 ` [PATCH libdrm 3/6] amdgpu: add handle table implementation Christian König
[not found] ` <20180802140452.23894-3-christian.koenig-5C7GfCeVMHo@public.gmane.org>
2018-08-02 14:55 ` Michel Dänzer
2018-08-02 15:24 ` William Lewis
2018-08-03 3:03 ` Zhang, Jerry (Junwei)
2018-08-02 14:04 ` [PATCH libdrm 4/6] amdgpu: use handle table for KMS handles Christian König
2018-08-02 14:04 ` [PATCH libdrm 5/6] amdgpu: use handle table for flink names Christian König
2018-08-02 14:04 ` [PATCH libdrm 6/6] amdgpu: remove the hash table implementation Christian König
2018-08-02 14:55 ` [PATCH libdrm 1/6] amdgpu: always add all BOs to lockup table Michel Dänzer
[not found] ` <2ede6f59-a1e6-fe9e-396f-2cc961db6df5-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-08-03 3:13 ` Zhang, Jerry (Junwei) [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=5B63C85B.6030103@amd.com \
--to=jerry.zhang-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=ckoenig.leichtzumerken-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=michel-otUistvHUpPR7s880joybQ@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.