Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423149AbXBBGa6 (ORCPT ); Fri, 2 Feb 2007 01:30:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423140AbXBBGa6 (ORCPT ); Fri, 2 Feb 2007 01:30:58 -0500 Received: from terminus.zytor.com ([192.83.249.54]:51901 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423151AbXBBGa5 (ORCPT ); Fri, 2 Feb 2007 01:30:57 -0500 Message-ID: <45C2DA8D.4050007@zytor.com> Date: Thu, 01 Feb 2007 22:30:37 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 To: Jeff Garzik CC: "Michael K. Edwards" , Linux Kernel List Subject: Re: Should io(read|write)(8|16|32)_rep take (const|) volatile u(8|16|32) __iomem *addr? References: <45C2D47A.9080001@garzik.org> In-Reply-To: <45C2D47A.9080001@garzik.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 501 Lines: 14 Jeff Garzik wrote: > Volatile is usually reserved for a specific need on a specific arch. I > doubt it is correct to force it on all arches. They already are volatile; the issue is adding "const". All io(read|write)* pointers are volatile, IIRC. -hpa - 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/