From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965369AbbJ0Tyu (ORCPT ); Tue, 27 Oct 2015 15:54:50 -0400 Received: from smtp2.provo.novell.com ([137.65.250.81]:38655 "EHLO smtp2.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965291AbbJ0Tyl (ORCPT ); Tue, 27 Oct 2015 15:54:41 -0400 From: Davidlohr Bueso To: Ingo Molnar , Peter Zijlstra Cc: Thomas Gleixner , Linus Torvalds , "Paul E. McKenney" , dave@stgolabs.net, linux-kernel@vger.kernel.org Subject: [PATCH 4/4] doc,smp: Remove ambiguous statement in smp_store_mb() Date: Tue, 27 Oct 2015 12:53:51 -0700 Message-Id: <1445975631-17047-5-git-send-email-dave@stgolabs.net> X-Mailer: git-send-email 2.1.4 In-Reply-To: <1445975631-17047-1-git-send-email-dave@stgolabs.net> References: <1445975631-17047-1-git-send-email-dave@stgolabs.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org It serves no purpose but to confuse readers, and is most likely a left over from constant memory-barriers.txt updates. Ie: http://lists.openwall.net/linux-kernel/2006/07/15/27 Signed-off-by: Davidlohr Bueso --- Documentation/memory-barriers.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt index b5fe765..ee6fbb0 100644 --- a/Documentation/memory-barriers.txt +++ b/Documentation/memory-barriers.txt @@ -1683,8 +1683,8 @@ There are some more advanced barrier functions: (*) smp_store_mb(var, value) This assigns the value to the variable and then inserts a full memory - barrier after it, depending on the function. It isn't guaranteed to - insert anything more than a compiler barrier in a UP compilation. + barrier after it. It isn't guaranteed to insert anything more than a + compiler barrier in a UP compilation. (*) smp_mb__before_atomic(); -- 2.1.4