From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: adaplas@gmail.com
Subject: Re: [PATCH] Free when fb can't be registered in video/aty/atyfb_base.c
Date: Fri, 26 Oct 2007 20:25:46 -0700 [thread overview]
Message-ID: <20071026202546.53b78732.randy.dunlap@oracle.com> (raw)
In-Reply-To: <47229AAA.9020907@tiscali.nl>
On Sat, 27 Oct 2007 03:55:54 +0200 Roel Kluin wrote:
> I am a bit uncertain about this one, but I think a 'free' is required here?
> --
> Free buffer when the framebuffer can't be registered
>
> Signed-off-by: Roel Kluin <12o3l@tiscali.nl>
> ---
> diff --git a/drivers/video/aty/atyfb_base.c b/drivers/video/aty/atyfb_base.c
> index d775eb6..7ccc78e 100644
> --- a/drivers/video/aty/atyfb_base.c
> +++ b/drivers/video/aty/atyfb_base.c
> @@ -2680,10 +2680,13 @@ static int __devinit aty_init(struct fb_info *info)
> #endif /* CONFIG_FB_ATY_CT */
> info->var = var;
>
> - fb_alloc_cmap(&info->cmap, 256, 0);
> + if (fb_alloc_cmap(&info->cmap, 256, 0) < 0)
> + goto aty_init_exit;
>
> - if (register_framebuffer(info) < 0)
> + if (register_framebuffer(info) < 0) {
> + fb_dealloc_cmap(&info->cmap);
Use tabs for indent above, not spaces.
Yes, looks needed to me. Hopefully Tony will correct us if we
are wrong.
Also appears to be needed in:
68328fb.c, ambaclcd.c, asiliantfb.c, atafb.c, ...
(I stopped looking for now.)
> goto aty_init_exit;
> + }
>
> fb_list = info;
>
---
~Randy
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-27 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 1:55 [PATCH] Free when fb can't be registered in video/aty/atyfb_base.c Roel Kluin
2007-10-27 3:25 ` Randy Dunlap [this message]
2007-10-27 12:31 ` Roel Kluin
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=20071026202546.53b78732.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).