Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750911AbbD3L5d (ORCPT ); Thu, 30 Apr 2015 07:57:33 -0400 Received: from e8.ny.us.ibm.com ([32.97.182.138]:53330 "EHLO e8.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705AbbD3L5b (ORCPT ); Thu, 30 Apr 2015 07:57:31 -0400 Subject: [PATCH] kernel: Replace reference to ASSIGN_ONCE with WRITE_ONCE in comment From: Preeti U Murthy To: borntraeger@de.ibm.com Cc: peterz@infradead.org, paulmck@linux.vnet.ibm.com, dave@stgolabs.net, linux-kernel@vger.kernel.org Date: Thu, 30 Apr 2015 17:27:21 +0530 Message-ID: <20150430115721.22278.94082.stgit@preeti.in.ibm.com> User-Agent: StGit/0.17-dirty MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15043011-0029-0000-0000-0000028DAAA4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1118 Lines: 31 Looks like commit : 43239cbe79fc ("kernel: Change ASSIGN_ONCE(val, x) to WRITE_ONCE(x, val)") left behind a reference to ASSIGN_ONCE. Update this to WRITE_ONCE. Signed-off-by: Preeti U Murthy --- include/linux/compiler.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/compiler.h b/include/linux/compiler.h index 0e41ca0..e65e0a7 100644 --- a/include/linux/compiler.h +++ b/include/linux/compiler.h @@ -446,7 +446,7 @@ static __always_inline void __write_once_size(volatile void *p, void *res, int s * with an explicit memory barrier or atomic instruction that provides the * required ordering. * - * If possible use READ_ONCE/ASSIGN_ONCE instead. + * If possible use READ_ONCE/WRITE_ONCE instead. */ #define __ACCESS_ONCE(x) ({ \ __maybe_unused typeof(x) __var = (__force typeof(x)) 0; \ -- 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/