From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751939AbbJLHqo (ORCPT ); Mon, 12 Oct 2015 03:46:44 -0400 Received: from mail-lb0-f177.google.com ([209.85.217.177]:35088 "EHLO mail-lb0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751842AbbJLHqm (ORCPT ); Mon, 12 Oct 2015 03:46:42 -0400 From: Rasmus Villemoes To: Peter Zijlstra , Ingo Molnar Cc: linux-kernel@vger.kernel.org, Rasmus Villemoes Subject: [PATCH] linux/compiler.h: fix stale comment on {READ,WRITE}_ONCE Date: Mon, 12 Oct 2015 09:46:21 +0200 Message-Id: <1444635981-25552-1-git-send-email-linux@rasmusvillemoes.dk> X-Mailer: git-send-email 2.1.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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, -- 2.1.3