From: Eric Anholt <eric@anholt.net>
To: DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 4/4] drm/vc4: Don't use drm_put_dev
Date: Fri, 09 Dec 2016 15:44:42 -0800 [thread overview]
Message-ID: <8760msvf9x.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <20161208110739.24417-4-daniel.vetter@ffwll.ch>
[-- Attachment #1.1: Type: text/plain, Size: 300 bytes --]
Daniel Vetter <daniel.vetter@ffwll.ch> writes:
> vc4 already has a proper load sequence, but the unload one needed some
> fixups: First unregister, and last drop the final ref.
>
> Cc: Eric Anholt <eric@anholt.net>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Pulled this one. Thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 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
next prev parent reply other threads:[~2016-12-09 23:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 11:07 [PATCH 1/4] drm/etnaviv: Use drm_dev_unref, not drm_put_dev Daniel Vetter
2016-12-08 11:07 ` [PATCH 2/4] drm/fsl: don't use drm_put_dev Daniel Vetter
2016-12-13 10:53 ` Lucas Stach
2016-12-13 17:12 ` Daniel Vetter
2016-12-13 17:54 ` [PATCH] " Daniel Vetter
2016-12-13 17:57 ` Lucas Stach
2016-12-13 21:26 ` Daniel Vetter
2016-12-13 23:29 ` Stefan Agner
2016-12-08 11:07 ` [PATCH 3/4] drm/mediatek: " Daniel Vetter
2016-12-13 10:55 ` Lucas Stach
2016-12-13 17:14 ` Daniel Vetter
2016-12-08 11:07 ` [PATCH 4/4] drm/vc4: Don't " Daniel Vetter
2016-12-09 23:44 ` Eric Anholt [this message]
2016-12-13 10:52 ` [PATCH 1/4] drm/etnaviv: Use drm_dev_unref, not drm_put_dev Lucas Stach
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=8760msvf9x.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.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