Re: [PATCH] arm: it's OK to pass pointer to volatile as iounmap() argument...

Hi!

> --- a/arch/arm/mm/ioremap.c
> +++ b/arch/arm/mm/ioremap.c
> @@ -361,14 +361,14 @@ __ioremap(unsigned long phys_addr, size_
>  }
>  EXPORT_SYMBOL(__ioremap);
>  
> -void __iounmap(void __iomem *addr)
> +void __iounmap(volatile void __iomem *addr)

Who is crazy enough to pass volatile pointers here? I guess they should be
fixed, instead.

							Pavel
-- 
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] arm: it's OK to pass pointer to volatile as iounmap() argument...
    • From: Al Viro <[email protected]>

• Prev by Date: Re: [uml-devel] [PATCH 01/14] uml: fix compilation options for USER_OBJS
• Next by Date: Re: [PATCH] use %p for pointers
• Previous by thread: [PATCH] arm: it's OK to pass pointer to volatile as iounmap() argument...
• Next by thread: [PATCH] lockdep: use BUILD_BUG_ON
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]