From: Tom St Denis <tom.stdenis-5C7GfCeVMHo@public.gmane.org>
To: christian.koenig-5C7GfCeVMHo@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/amd/amdgpu: Avoid fault when allocating an empty buffer object
Date: Mon, 17 Sep 2018 14:11:06 -0400 [thread overview]
Message-ID: <7c6591c4-906f-d5f3-05a5-a1a0e514ffbc@amd.com> (raw)
In-Reply-To: <9d13625d-f0da-cf16-2e0a-78db28dc7a1a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 2018-09-17 2:08 p.m., Christian König wrote:
> Am 17.09.2018 um 20:07 schrieb Tom St Denis:
>> Signed-off-by: Tom St Denis <tom.stdenis@amd.com>
>
> Reviewed-by: Christian König <christian.koenig@amd.com>
>
> You was faster than me :)
Been a while since I got a patch on the kernel side... need to keep up
numbers :-)
Tom
>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> index 84d82d5382f9..c1387efc0c91 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> @@ -348,7 +348,8 @@ int amdgpu_bo_create_kernel(struct amdgpu_device
>> *adev,
>> if (r)
>> return r;
>> - amdgpu_bo_unreserve(*bo_ptr);
>> + if (*bo_ptr)
>> + amdgpu_bo_unreserve(*bo_ptr);
>> return 0;
>> }
>
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-09-17 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 18:07 [PATCH] drm/amd/amdgpu: Avoid fault when allocating an empty buffer object Tom St Denis
[not found] ` <20180917180711.29594-1-tom.stdenis-5C7GfCeVMHo@public.gmane.org>
2018-09-17 18:08 ` Christian König
[not found] ` <9d13625d-f0da-cf16-2e0a-78db28dc7a1a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-09-17 18:11 ` Tom St Denis [this message]
2018-09-18 5:49 ` Huang Rui
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=7c6591c4-906f-d5f3-05a5-a1a0e514ffbc@amd.com \
--to=tom.stdenis-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=christian.koenig-5C7GfCeVMHo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox