From: Dan Carpenter <dan.carpenter@oracle.com>
To: Emil Goode <emilgoode@gmail.com>
Cc: FlorianSchandinat@gmx.de, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] video: bfin_adv7393fb: Fix cleanup code
Date: Mon, 28 May 2012 15:26:01 +0000 [thread overview]
Message-ID: <20120528152601.GE4637@mwanda> (raw)
In-Reply-To: <1338216019-1288-1-git-send-email-emilgoode@gmail.com>
On Mon, May 28, 2012 at 04:40:19PM +0200, Emil Goode wrote:
> This patch fixes the cleanup code of the bfin_adv7393_fb_probe
> function by changing the order in which cleanup is performed
> and by adding one label.
>
Could you list the actual bugs which were fixed:
1) The resources were not freed in the order that we allocated them
so we call dma_free_coherent() before it was allocated.
2) The labels weren't in the right place which also meant that we
freed resources that weren't allocated.
3) We should free gpio_free(P_IDENT(P_PPI0_FS3)) before returning.
The new gpio_free() is more important than the added label.
Since you're changing all these, you may as well fix the label names
as well. The out_9 style labels suck. The right way is to give
them meaningful labels instead of GW-BASIC style labels.
Labels should be named after what happens when you arrive. Some
people name them after the start of the journey but that's a
mistake. It's just like the town of Chicago is still called Chicago
even though you might goto Chicago starting from Boston. Like this:
err_ppi:
free_dma(CH_PPI);
fb_dealloc_cmap(&fbdev->info.cmap);
err_palette:
kfree(fbdev->info.pseudo_palette);
regards,
dan carpenter
next prev parent reply other threads:[~2012-05-28 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 14:40 [PATCH] video: bfin_adv7393fb: Fix cleanup code Emil Goode
2012-05-28 15:26 ` Dan Carpenter [this message]
2012-05-28 15:34 ` Emil Goode
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=20120528152601.GE4637@mwanda \
--to=dan.carpenter@oracle.com \
--cc=FlorianSchandinat@gmx.de \
--cc=emilgoode@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--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).