All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: mawilcox@microsoft.com, airlied@linux.ie,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	briannorris@chromium.org, dri-devel@lists.freedesktop.org,
	"Cihangir Aktürk" <cakturk@gmail.com>,
	dan.carpenter@oracle.com
Subject: Re: [PATCH] drm/vgem: Replace drm_dev_unref with drm_dev_put
Date: Mon, 16 Jul 2018 11:12:29 +0200	[thread overview]
Message-ID: <0b89ed5f-d3b6-b249-105d-c093e28c030c@suse.de> (raw)
In-Reply-To: <CAFqt6zY-YX_f4i8yhX85xkgZVC65KSVQkxLLdK-rUpKhcOL4_Q@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 659 bytes --]

Hi

> There are other gpu/drm drivers where drm_dev_unref is used.
> Do we need to replace drm_dev_unref with drm_dev_put  in
> other places as well ?

Yes. This is some overall clean-up work that I do as a side project. I
already have patches for all drivers, but I found that sending them
one-by-one gives a much better chance of getting them applied.

Best regards
Thomas

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755;  https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-07-16  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  7:46 [PATCH] drm/vgem: Replace drm_dev_unref with drm_dev_put Thomas Zimmermann
2018-07-16  9:07 ` Souptick Joarder
2018-07-16  9:12   ` Thomas Zimmermann [this message]
2018-08-09 12:46 ` 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=0b89ed5f-d3b6-b249-105d-c093e28c030c@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@linux.ie \
    --cc=briannorris@chromium.org \
    --cc=cakturk@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jrdr.linux@gmail.com \
    --cc=mawilcox@microsoft.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 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.