Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423125AbXBBGEp (ORCPT ); Fri, 2 Feb 2007 01:04:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423124AbXBBGEp (ORCPT ); Fri, 2 Feb 2007 01:04:45 -0500 Received: from srv5.dvmed.net ([207.36.208.214]:45774 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423125AbXBBGEo (ORCPT ); Fri, 2 Feb 2007 01:04:44 -0500 Message-ID: <45C2D47A.9080001@garzik.org> Date: Fri, 02 Feb 2007 01:04:42 -0500 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 To: "Michael K. Edwards" CC: Linux Kernel List Subject: Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr? References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.3 (----) X-Spam-Report: SpamAssassin version 3.1.7 on srv5.dvmed.net summary: Content analysis details: (-4.3 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 374 Lines: 12 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/