Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1244677ybb; Fri, 20 Mar 2020 16:25:43 -0700 (PDT) X-Google-Smtp-Source: ADFU+vv2N6Lx39+j20vJ9d/Zz/N8uCQsAcbFBkdsCjG5ru1/kVrkW5pr7KzGsPUykHg/A1/8niD1 X-Received: by 2002:a9d:364b:: with SMTP id w69mr8998471otb.332.1584746743707; Fri, 20 Mar 2020 16:25:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584746743; cv=none; d=google.com; s=arc-20160816; b=UPg2cvP++E7y5z6/0WxY3QdN8+C4+8Dh3sPKbf/xlbG0oHeymB0hcIDdpONV7KEr5q aJX3ktXeB3Bejsviso++IYhyRpv/2nwngNL5HU2/Sp6cZAfcin8D1GKLLCYmZ1NAhfL0 9ep0TDUt4wurtCSg+CA1ZK1g8/G2vtj/Ne+uo+h5qtK44hveff3aaxd5rHRm+ZRMQ5fu YJvzyNbnrsNhnq+ZuCAK747PiNrbIA5vrJ9vlPmuKrySXx/Q5fDM/NmiXCmTsGNkNMAA PgKo3CHwHud3PB7MAv1Nbv17RBDHJtsIQvjdA6arRSSzpi+o74j8Kshb5uYmKcDwQl5/ TfYw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=4lh9DH2ubgk0up3Erw+fCUEFqnK5h87Rt1uO4b54joM=; b=RSF0S59tChYXMwdiU3+cLPuZImFbAlYpLQ7pNqt230fcCQUhU239A76oMYECqMX5qE 0WKOHDxwxm3zankXMFSNRIwTxazfc3IOvxqmYuZYie92DjTO06CF3gSfCagiD6/UO51z QATDzCLa7CbV2yzebMshUYLPd9WvsJGK9+lf/vLeFuJzVIggmz7+knCE3Uso+OZ+uEvW B80+WoY35QtJVpk3q9crRLnBXK6TTv6FzHsuTQeWE7kTjmBAbO96u7fBTAC0VLZyB7dt OVx1KGKseEm/4vI7ESaNtP4HiQRaaGu/uEXZ3h6hROpqOcE5w9L3pnwApctNx3wQM2ag WyUQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w12si3740709ote.179.2020.03.20.16.25.30; Fri, 20 Mar 2020 16:25:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727567AbgCTXY2 (ORCPT + 99 others); Fri, 20 Mar 2020 19:24:28 -0400 Received: from ms.lwn.net ([45.79.88.28]:44132 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726738AbgCTXY2 (ORCPT ); Fri, 20 Mar 2020 19:24:28 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 7B4522D6; Fri, 20 Mar 2020 23:24:27 +0000 (UTC) Date: Fri, 20 Mar 2020 17:24:26 -0600 From: Jonathan Corbet To: Wang Wenhu Cc: Harry Wei , Alex Shi , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@vivo.com Subject: Re: [PATCH v2,RESEND] doc: zh_CN: fix style problems for io_ordering.txt Message-ID: <20200320172426.121d881d@lwn.net> In-Reply-To: <20200315060857.82880-1-wenhu.wang@vivo.com> References: <20200315060857.82880-1-wenhu.wang@vivo.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 14 Mar 2020 23:08:55 -0700 Wang Wenhu wrote: > Problems exist in the Chinese translation of io_ordering.txt. > Partly for the difference between Chinese and English character > encoding format, and the others are of the failure to comply > with the ReST markups. So I feel like I'm missing something here... > Signed-off-by: Wang Wenhu > --- > v2: resend for the failure of delivering. > > .../translations/zh_CN/io_ordering.txt | 72 ++++++++++++------- > 1 file changed, 46 insertions(+), 26 deletions(-) > > diff --git a/Documentation/translations/zh_CN/io_ordering.txt b/Documentation/translations/zh_CN/io_ordering.txt > index 1f8127bdd415..080ed2911db0 100644 > --- a/Documentation/translations/zh_CN/io_ordering.txt > +++ b/Documentation/translations/zh_CN/io_ordering.txt > @@ -29,39 +29,59 @@ Documentation/io_ordering.txt 的中文翻译 > 这也可以保证后面的写操作只在前面的写操作之后到达设备(这非常类似于内存 > 屏障操作,mb(),不过仅适用于I/O)。 > > +A more concrete example from a hypothetical device driver:: > + > + ... > + CPU A: spin_lock_irqsave(&dev_lock, flags) > + CPU A: val = readl(my_status); > + CPU A: ... > + CPU A: writel(newval, ring_ptr); > + CPU A: spin_unlock_irqrestore(&dev_lock, flags) > + ... > + CPU B: spin_lock_irqsave(&dev_lock, flags) > + CPU B: val = readl(my_status); > + CPU B: ... > + CPU B: writel(newval2, ring_ptr); > + CPU B: spin_unlock_irqrestore(&dev_lock, flags) > + ... > + > + > 假设一个设备驱动程的具体例子: > +:: > > + ... > + CPU A: spin_lock_irqsave(&dev_lock, flags) > + CPU A: val = readl(my_status); > + CPU A: ... > + CPU A: writel(newval, ring_ptr); > + CPU A: spin_unlock_irqrestore(&dev_lock, flags) > + ... > + CPU B: spin_lock_irqsave(&dev_lock, flags) > + CPU B: val = readl(my_status); > + CPU B: ... > + CPU B: writel(newval2, ring_ptr); > + CPU B: spin_unlock_irqrestore(&dev_lock, flags) It sure looks like you're adding the same text twice here...? Thanks, jon