Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760185AbXEJQUc (ORCPT ); Thu, 10 May 2007 12:20:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755024AbXEJQU1 (ORCPT ); Thu, 10 May 2007 12:20:27 -0400 Received: from orion2.pixelized.ch ([195.190.190.13]:38443 "EHLO mail.pixelized.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754775AbXEJQU0 (ORCPT ); Thu, 10 May 2007 12:20:26 -0400 X-Greylist: delayed 322 seconds by postgrey-1.27 at vger.kernel.org; Thu, 10 May 2007 12:20:26 EDT Message-ID: <464344FD.6000809@cateee.net> Date: Thu, 10 May 2007 18:14:53 +0200 From: "Giacomo A. Catenazzi" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Jonathan Corbet CC: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, Randy Dunlap Subject: Re: [PATCH] "volatile considered harmful" document References: <25493.1178744744@lwn.net> In-Reply-To: <25493.1178744744@lwn.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 18 Jonathan Corbet wrote: > +The volatile storage class was originally meant for memory-mapped I/O > +registers. Within the kernel, register accesses, too, should be protected I don't think it deserves to be added in documentation, but just for reference: in userspace "volatile" is needed in signals (posix mandates some variables to be volatile, as API, not as funtionality). I don't know if this was also on the original signal handling. Anyway user space APIs are not kernel problem ;-) ciao cate - 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/