dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65121] Possible memory leak in qxl drm driver
Date: Fri, 20 Jun 2014 04:45:32 +0000	[thread overview]
Message-ID: <bug-65121-2300-GIGhRgBcmI@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65121-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=65121

--- Comment #11 from xerofoify@gmail.com ---
It seems to be only the opener or maintainer of this subsystem who can close
it.
Cheers Nick

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-06-20  4:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65121-2300@https.bugzilla.kernel.org/>
2013-11-26 22:06 ` [Bug 65121] Possible memory leak in qxl drm driver bugzilla-daemon
2013-11-28  5:29 ` bugzilla-daemon
2013-11-28  5:41 ` bugzilla-daemon
2013-11-29  5:27 ` bugzilla-daemon
2014-06-20  4:09 ` bugzilla-daemon
2014-06-20  4:34 ` bugzilla-daemon
2014-06-20  4:43 ` bugzilla-daemon
2014-06-20  4:45 ` bugzilla-daemon [this message]
2014-06-20 15:35 ` bugzilla-daemon

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=bug-65121-2300-GIGhRgBcmI@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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