From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752805AbcGUOMG (ORCPT ); Thu, 21 Jul 2016 10:12:06 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:20215 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750856AbcGUOLu (ORCPT ); Thu, 21 Jul 2016 10:11:50 -0400 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com Date: Thu, 21 Jul 2016 07:11:53 -0700 From: "Paul E. McKenney" To: SeongJae Park Cc: byungchul.park@lge.com, corbet@lwn.net, mingo@kernel.org, dhowells@redhat.com, minchan@kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [PATCH v5 1/2] Doc/memory-barriers: Fix a typo of example result Reply-To: paulmck@linux.vnet.ibm.com References: <1469063458-6573-1-git-send-email-sj38.park@gmail.com> <1469063458-6573-2-git-send-email-sj38.park@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1469063458-6573-2-git-send-email-sj38.park@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16072114-0024-0000-0000-000014285036 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16072114-0025-0000-0000-000042E21127 Message-Id: <20160721141153.GQ7094@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-07-21_06:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607210156 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 21, 2016 at 10:10:57AM +0900, SeongJae Park wrote: > An example result for data dependent write has a typo. This commit > fixes the wrong typo. > > Signed-off-by: SeongJae Park Good catch! Queued, thank you! Thanx, Paul > --- > Documentation/memory-barriers.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt > index 19c8eb6..ba818ec 100644 > --- a/Documentation/memory-barriers.txt > +++ b/Documentation/memory-barriers.txt > @@ -609,7 +609,7 @@ A data-dependency barrier must also order against dependent writes: > The data-dependency barrier must order the read into Q with the store > into *Q. This prohibits this outcome: > > - (Q == B) && (B == 4) > + (Q == &B) && (B == 4) > > Please note that this pattern should be rare. After all, the whole point > of dependency ordering is to -prevent- writes to the data structure, along > -- > 1.9.1 >