From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Thierry Reding <thierry.reding@avionic-design.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: Keep a reference to the active plane framebuffer
Date: Tue, 19 Feb 2013 17:32:56 +0200 [thread overview]
Message-ID: <20130219153256.GS9135@intel.com> (raw)
In-Reply-To: <1361287087-32035-1-git-send-email-thierry.reding@avionic-design.de>
On Tue, Feb 19, 2013 at 04:18:07PM +0100, Thierry Reding wrote:
> When updating a plane, the DRM core always sets the plane's framebuffer
> to NULL. This in turn will cause the reference count on the plane's
> active framebuffer to become unbalanced because on the next update, the
> old framebuffer will be NULL.
>
> Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
http://lists.freedesktop.org/archives/dri-devel/2013-February/034978.html
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-02-19 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 15:18 [PATCH] drm: Keep a reference to the active plane framebuffer Thierry Reding
2013-02-19 15:32 ` Ville Syrjälä [this message]
2013-02-19 15:36 ` Thierry Reding
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=20130219153256.GS9135@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=thierry.reding@avionic-design.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox