From: Andrew Morton <akpm@linux-foundation.org>
To: Julia Lawall <julia@diku.dk>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
kernel-janitors@vger.kernel.org, rtc-linux@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/rtc/rtc-mrst.c: Use release_mem_region after
Date: Thu, 07 Apr 2011 23:01:42 +0000 [thread overview]
Message-ID: <20110407160142.0a9d399c.akpm@linux-foundation.org> (raw)
In-Reply-To: <1300136425-3311-1-git-send-email-julia@diku.dk>
On Mon, 14 Mar 2011 22:00:25 +0100
Julia Lawall <julia@diku.dk> wrote:
> The memory allocated using request_mem_region should be released using
> release_mem_region, not release_region.
>
> The semantic patch that fixes part of this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> // <smpl>
> @@
> expression E1,E2,E3;
> @@
>
> request_mem_region(E1,E2,E3)
> ...
> ?- release_region(E1,E2)
> + release_mem_region(E1,E2)
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> drivers/rtc/rtc-mrst.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/rtc/rtc-mrst.c b/drivers/rtc/rtc-mrst.c
> index b86bc32..558dd7d 100644
> --- a/drivers/rtc/rtc-mrst.c
> +++ b/drivers/rtc/rtc-mrst.c
> @@ -379,7 +379,7 @@ cleanup1:
> mrst_rtc.dev = NULL;
> rtc_device_unregister(mrst_rtc.rtc);
> cleanup0:
> - release_region(iomem->start, iomem->end + 1 - iomem->start);
> + release_mem_region(iomem->start, iomem->end + 1 - iomem->start);
> dev_err(dev, "rtc-mrst: unable to initialise\n");
> return retval;
> }
> @@ -405,7 +405,7 @@ static void __exit rtc_mrst_do_remove(struct device *dev)
> mrst->rtc = NULL;
>
> iomem = mrst->iomem;
> - release_region(iomem->start, iomem->end + 1 - iomem->start);
> + release_mem_region(iomem->start, iomem->end + 1 - iomem->start);
> mrst->iomem = NULL;
>
> mrst->dev = NULL;
We may as well clean this up too.
--- a/drivers/rtc/rtc-mrst.c~drivers-rtc-rtc-mrstc-use-release_mem_region-after-request_mem_region-fix
+++ a/drivers/rtc/rtc-mrst.c
@@ -380,7 +380,7 @@ cleanup1:
cleanup0:
dev_set_drvdata(dev, NULL);
mrst_rtc.dev = NULL;
- release_mem_region(iomem->start, iomem->end + 1 - iomem->start);
+ release_mem_region(iomem->start, resource_size(iomem));
dev_err(dev, "rtc-mrst: unable to initialise\n");
return retval;
}
@@ -406,7 +406,7 @@ static void __devexit rtc_mrst_do_remove
mrst->rtc = NULL;
iomem = mrst->iomem;
- release_mem_region(iomem->start, iomem->end + 1 - iomem->start);
+ release_mem_region(iomem->start, resource_size(iomem));
mrst->iomem = NULL;
mrst->dev = NULL;
_
which makes one wonder why we don't have
void release_resource_mem(struct resource *r)
{
release_mem_region(r->start, resource_size(r));
}
next prev parent reply other threads:[~2011-04-07 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 20:58 [PATCH] drivers/rtc/rtc-mrst.c: Use release_mem_region after request_mem_region Julia Lawall
2011-04-07 23:01 ` Andrew Morton [this message]
2011-04-08 5:14 ` [PATCH] drivers/rtc/rtc-mrst.c: Use release_mem_region after Julia Lawall
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=20110407160142.0a9d399c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.zummo@towertech.it \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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