From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] ioremap() / iounmap() balancing problem in scoop_probe() ?
Date: Mon, 11 Apr 2005 08:42:48 +0000 [thread overview]
Message-ID: <20050411084247.GA3958@nd47.coderock.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0504102318150.15064@s1.ckr-solutions.com>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On 10/04/05 23:23 +0200, Olivier Kaloudoff wrote:
> Hi,
>
>
> following the advice of Bertl, I'm trying my first error
> report about the scoop device driver for arm, kernel 2.6.11.5;
Great!
>
> I found that scoop_io_base is only used in scoop.c (once),
> so after use, the memory area should be freed;
Code seems different now (2.6.12-rc2).
>
>
> root@nec:/usr/src/linux/arch/arm/common# diff -Naur scoop.c.orig scoop.c
> --- scoop.c.orig 2005-04-10 23:17:06.000000000 +0200
> +++ scoop.c 2005-04-10 23:17:28.000000000 +0200
patch -p1 appliable patches please.
> @@ -107,6 +107,7 @@
> scoop_io_base = ioremap(mem->start, 0x1000);
Tabs converted to spaces. (copy & paste? try "insert file" or similar)
> if (!scoop_io_base)
> return -ENOMEM;
> + iounmap(scoop_io_base);
I think the right usage is as it is in -rc2 (code seems a bit changed),
iounmap in remove() after we stop using it.
>
> SCOOP_REG(SCOOP_MCR) = 0x0140;
>
>
> Am I right ?
>
>
> Olivier
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/kernel-janitors
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-04-11 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 21:23 [KJ] ioremap() / iounmap() balancing problem in scoop_probe() ? Olivier Kaloudoff
2005-04-11 8:42 ` Domen Puncer [this message]
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=20050411084247.GA3958@nd47.coderock.org \
--to=domen@coderock.org \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.