The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Cihangir Akturk <cakturk@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Hans de Goede <hdegoede@redhat.com>,
	Michael Thayer <michael.thayer@oracle.com>,
	devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: vboxvideo: use drm_gem_object_put instead of drm_gem_object_unreference
Date: Wed, 2 Aug 2017 16:47:56 +0300	[thread overview]
Message-ID: <20170802134756.GA796@mbp> (raw)
In-Reply-To: <CAKMK7uF2H+JrEgbPxT7O3R37mLM4s1xzmtoBRPP55KCxW7vgsg@mail.gmail.com>

On Wed, Aug 02, 2017 at 02:38:50PM +0200, Daniel Vetter wrote:
> On Wed, Aug 2, 2017 at 1:46 AM, Cihangir Akturk <cakturk@gmail.com> wrote:
> > drm_gem_object_unreference is a compatibility alias for drm_gem_object_put so should
> > not be used by new code.
> >
> > This patch fixes the following warning reported by coccinelle:
> >
> > drivers/staging/vboxvideo/vbox_main.c:528:1-27: WARNING: use get/put
> > helpers to reference and dereference obj
> >
> > Signed-off-by: Cihangir Akturk <cakturk@gmail.com>
> 
> Care to do this for all the drm drivers, not just the single one in staging?

Sure, I'll send a v2 shortly as you suggested.

Thanks.

> 
> Hans/Greg: Can we pls fix up MAINTAINERS to make sure vboxdrm patches
> also go to dri-devel?
> 
> Thanks, Daniel

  reply	other threads:[~2017-08-02 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1501631202-11656-1-git-send-email-cakturk@gmail.com>
2017-08-02 12:38 ` [PATCH] staging: vboxvideo: use drm_gem_object_put instead of drm_gem_object_unreference Daniel Vetter
2017-08-02 13:47   ` Cihangir Akturk [this message]
2017-08-02 14:17     ` Daniel Vetter

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=20170802134756.GA796@mbp \
    --to=cakturk@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.thayer@oracle.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