public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Daeseok Youn <daeseok.youn@gmail.com>
Cc: devel@driverdev.osuosl.org, lidza.louina@gmail.com,
	driverdev-devel@linuxdriverproject.org,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 2/3] staging: dgap: adds missing iounmap for re_map_port in dgap_release_remap()
Date: Wed, 24 Sep 2014 12:42:29 +0300	[thread overview]
Message-ID: <20140924094229.GB5811@mwanda> (raw)
In-Reply-To: <20140924093648.GA5811@mwanda>

On Wed, Sep 24, 2014 at 12:36:48PM +0300, Dan Carpenter wrote:
> On Tue, Sep 23, 2014 at 09:22:08AM +0900, Daeseok Youn wrote:
> > Signed-off-by: Daeseok Youn <daeseok.youn@gmail.com>
> > ---
> >  drivers/staging/dgap/dgap.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > diff --git a/drivers/staging/dgap/dgap.c b/drivers/staging/dgap/dgap.c
> > index 779d144..637ea8a 100644
> > --- a/drivers/staging/dgap/dgap.c
> > +++ b/drivers/staging/dgap/dgap.c
> > @@ -1026,6 +1026,7 @@ static void dgap_release_remap(struct board_t *brd)
> >  	release_mem_region(brd->membase, 0x200000);
> >  	release_mem_region(brd->membase + PCI_IO_OFFSET, 0x200000);
> >  	iounmap(brd->re_map_membase);
> > +	iounmap(brd->re_map_port);
> 
> 
> I don't think it matters, but at least aesthetically it would be better
> to unmap first and then release the regions.  (You can do this in a
> different patch).
> 

Also dgap_do_remap() unwinds in the wrong order and is sucky.  It should
use gotos.

Also the name dgap_do_remap() isn't great.  Remap is a verb not a noun
so the "_do" isn't needed.  Just dgap_remap() and dgap_release_remap()
could be changed to dgap_unmap().

regards,
dan carpenter


  reply	other threads:[~2014-09-24  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  0:22 [PATCH 2/3] staging: dgap: adds missing iounmap for re_map_port in dgap_release_remap() Daeseok Youn
2014-09-24  9:36 ` Dan Carpenter
2014-09-24  9:42   ` Dan Carpenter [this message]
2014-09-25  0:21     ` DaeSeok Youn

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=20140924094229.GB5811@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=daeseok.youn@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lidza.louina@gmail.com \
    --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