From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752462AbbJLIAT (ORCPT ); Mon, 12 Oct 2015 04:00:19 -0400 Received: from e06smtp12.uk.ibm.com ([195.75.94.108]:35934 "EHLO e06smtp12.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751407AbbJLIAR (ORCPT ); Mon, 12 Oct 2015 04:00:17 -0400 X-IBM-Helo: d06dlp02.portsmouth.uk.ibm.com X-IBM-MailFrom: borntraeger@de.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Subject: Re: [PATCH] linux/compiler.h: fix stale comment on {READ,WRITE}_ONCE To: Rasmus Villemoes , Peter Zijlstra , Ingo Molnar References: <1444635981-25552-1-git-send-email-linux@rasmusvillemoes.dk> Cc: linux-kernel@vger.kernel.org From: Christian Borntraeger Message-ID: <561B688C.3040701@de.ibm.com> Date: Mon, 12 Oct 2015 10:00:12 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <1444635981-25552-1-git-send-email-linux@rasmusvillemoes.dk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15101208-0009-0000-0000-000005E56729 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 12.10.2015 um 09:46 schrieb Rasmus Villemoes: > Commit 7bd3e239d6c6 ("locking: Remove atomicy checks from > {READ,WRITE}_ONCE") removed said warning. > > Signed-off-by: Rasmus Villemoes > --- > include/linux/compiler.h | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/include/linux/compiler.h b/include/linux/compiler.h > index c836eb2dc44d..1dd0034e15e2 100644 > --- a/include/linux/compiler.h > +++ b/include/linux/compiler.h > @@ -237,8 +237,7 @@ static __always_inline void __write_once_size(volatile void *p, void *res, int s > * In contrast to ACCESS_ONCE these two macros will also work on aggregate > * data types like structs or unions. If the size of the accessed data > * type exceeds the word size of the machine (e.g., 32 bits or 64 bits) > - * READ_ONCE() and WRITE_ONCE() will fall back to memcpy and print a > - * compile-time warning. > + * READ_ONCE() and WRITE_ONCE() will fall back to memcpy. > * > * Their two major use cases are: (1) Mediating communication between > * process-level code and irq/NMI handlers, all running on the same CPU, > Acked-by: Christian Borntraeger