From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: hdegoede@redhat.com, michael.thayer@oracle.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] staging/vboxvideo: Replace ttm_bo_unref with ttm_bo_put
Date: Mon, 10 Sep 2018 10:42:38 +0200 [thread overview]
Message-ID: <20180910084238.GA7385@kroah.com> (raw)
In-Reply-To: <6bb021ce-63b7-da82-7f47-e3e5311a306d@suse.de>
On Mon, Sep 10, 2018 at 10:39:57AM +0200, Thomas Zimmermann wrote:
> Hi Greg
>
> Am 02.08.2018 um 09:29 schrieb Greg KH:
> > On Tue, Jul 31, 2018 at 08:37:35AM +0200, Thomas Zimmermann wrote:
> >> The function ttm_bo_put releases a reference to a TTM buffer object. The
> >> function's name is more aligned to the Linux kernel convention of naming
> >> ref-counting function _get and _put.
> >>
> >> A call to ttm_bo_unref takes the address of the TTM BO object's pointer and
> >> clears the pointer's value to NULL. This is not necessary in most cases and
> >> sometimes even worked around by the calling code. A call to ttm_bo_put only
> >> releases the reference without clearing the pointer.
> >>
> >> The current behaviour of cleaning the pointer is kept in the calling code,
> >> but should be removed if not required in a later patch.
> >>
> >> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> >> ---
> >> drivers/staging/vboxvideo/vbox_main.c | 5 ++---
> >> 1 file changed, 2 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/staging/vboxvideo/vbox_main.c b/drivers/staging/vboxvideo/vbox_main.c
> >> index 9d2018cd544e..fc7293b756b2 100644
> >> --- a/drivers/staging/vboxvideo/vbox_main.c
> >> +++ b/drivers/staging/vboxvideo/vbox_main.c
> >> @@ -490,9 +490,8 @@ static void vbox_bo_unref(struct vbox_bo **bo)
> >> return;
> >>
> >> tbo = &((*bo)->bo);
> >> - ttm_bo_unref(&tbo);
> >> - if (!tbo)
> >> - *bo = NULL;
> >> + ttm_bo_put(tbo);
> >
> > This function is not in my tree, so it causes a build error. I guess
> > merge this through the drm tree?
>
> The required function ttm_bo_put() is now available in mainline. [1] Can
> you please try again merging the patch? Thanks!
Sure, can you resend it please? This one is long gone from my patch
queue.
thanks,
greg k-h
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-10 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 6:37 [PATCH] staging/vboxvideo: Replace ttm_bo_unref with ttm_bo_put Thomas Zimmermann
2018-08-02 7:29 ` Greg KH
2018-08-02 7:52 ` Thomas Zimmermann
2018-09-10 8:39 ` Thomas Zimmermann
2018-09-10 8:42 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-10 9:36 Thomas Zimmermann
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=20180910084238.GA7385@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=michael.thayer@oracle.com \
--cc=tzimmermann@suse.de \
/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.