Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr?

• To: "Michael K. Edwards" <[email protected]>
• Subject: Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr?
• From: Jeff Garzik <[email protected]>
• Date: Fri, 02 Feb 2007 01:04:42 -0500
• Cc: Linux Kernel List <[email protected]>
• In-reply-to: <[email protected]>
• References: <[email protected]> <[email protected]>
• Sender: [email protected]
• User-agent: Thunderbird 1.5.0.9 (X11/20061219)

Volatile is usually reserved for a specific need on a specific arch. I doubt it is correct to force it on all arches.

	Jeff



-
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/

---

• Follow-Ups:
  • Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr?
    • From: "H. Peter Anvin" <[email protected]>

• References:
  • Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr?
    • From: "Michael K. Edwards" <[email protected]>

• Prev by Date: Re: [RFC 0/8] Cpuset aware writeback
• Next by Date: Re: [PATCH] Ban module license tag string termination trick
• Previous by thread: Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr?
• Next by thread: Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr?
• 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]