From: David Miller <davem@davemloft.net>
To: dilinger@queued.net
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com
Subject: Re: [PATCH 10/15] sunxvr500: fix cmap memory leaks
Date: Sun, 08 Feb 2009 16:59:25 -0800 (PST) [thread overview]
Message-ID: <20090208.165925.240846008.davem@davemloft.net> (raw)
In-Reply-To: <20090207121540.0e618d0f@ephemeral>
From: Andres Salomon <dilinger@queued.net>
Date: Sat, 7 Feb 2009 12:15:40 -0500
[ Fixed typo in adaplas's email address ]
> - fix cmap leak in removal path
> - fix cmap leak when register_framebuffer fails
>
> Signed-off-by: Andres Salomon <dilinger@debian.org>
I assume the fbdev folks will pick this up or should I take
it in my sparc tree?
Thanks.
next prev parent reply other threads:[~2009-02-09 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 17:15 [PATCH 10/15] sunxvr500: fix cmap memory leaks Andres Salomon
2009-02-09 0:59 ` David Miller [this message]
2009-02-09 1:50 ` Andrew Morton
2009-02-09 1:51 ` David Miller
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=20090208.165925.240846008.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).