From: Emil Velikov <emil.l.velikov@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"David Zhou" <David1.Zhou@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"amd-gfx mailing list" <amd-gfx@lists.freedesktop.org>,
"Emil Velikov" <emil.velikov@collabora.com>
Subject: Re: [PATCH] drm/amdgpu: fix leftover drm_gem_object_put_unlocked call
Date: Fri, 22 May 2020 20:46:31 +0100 [thread overview]
Message-ID: <CACvgo526v2Mv_U40k-xJyvMQUs-F87brcn+d6jtUrQ57Yq-j2Q@mail.gmail.com> (raw)
In-Reply-To: <CACvgo52rE4E+6B7NNM8=tPPsu3ouOP9MnY4CNCsDsN8U_odSeA@mail.gmail.com>
On Fri, 22 May 2020 at 20:43, Emil Velikov <emil.l.velikov@gmail.com> wrote:
>
> On Fri, 22 May 2020 at 20:38, Simon Ser <contact@emersion.fr> wrote:
> >
> > drm_gem_object_put_unlocked has been renamed to drm_gem_object_put.
> >
> > Signed-off-by: Simon Ser <contact@emersion.fr>
> > Fixes: e07ddb0ce7cd ("drm/amd: remove _unlocked suffix in drm_gem_object_put_unlocked")
> Wrong tag it seems. At that commit, the amdgpu code uses it's own
> wrapper - amdgpu_bo_unref()
>
Alex, team, this seems like merge clash.
With the Fixes tag dropped, the patch is:
Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com>
-Emil
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-05-22 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 19:38 [PATCH] drm/amdgpu: fix leftover drm_gem_object_put_unlocked call Simon Ser
2020-05-22 19:43 ` Emil Velikov
2020-05-22 19:46 ` Emil Velikov [this message]
2020-05-22 19:43 ` Felix Kuehling
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=CACvgo526v2Mv_U40k-xJyvMQUs-F87brcn+d6jtUrQ57Yq-j2Q@mail.gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=David1.Zhou@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=contact@emersion.fr \
--cc=emil.velikov@collabora.com \
/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;
as well as URLs for NNTP newsgroup(s).