Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2864625pxj; Mon, 10 May 2021 12:29:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzU/xl9O38oWH8nvMsMYzgSPme4oMTjYJPv010CWg+W1kKiIPEiOG5W8XqLOqBFDcCeb7OJ X-Received: by 2002:a92:1909:: with SMTP id 9mr22882056ilz.229.1620674986583; Mon, 10 May 2021 12:29:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620674986; cv=none; d=google.com; s=arc-20160816; b=hsz9mF6i6u3m/iwIjk55O7mscZj0lYCYfY4way7tmzkL146u3sUSbeHOD0BZT8o0hR 50zdaro28yKCirCKzlOpbYaRX9xXO2Xqefn+nb9rv3cveX5T6sO++5OPV5RsCizN/kfi HnZ8+N2rGGe70/snXN/BO8Y/dt5dKLucGCLfblYpsKGVYLH9w09JMpY8/AD3/QueCagw L/FViZvG6V6metGlKwRBHSyCGqylTeUOvffMpMmPjOFOHlE+Hw9ktpG4iCxgYG3lPggp bVJoOTQ3CHRA7AFIjseoLAHaSulA9SF5NGYakJnAINJBeLUNqfi/prXGlMQIBiFhP/fs qVDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=M6r3DxlNPkhf3OhaNDcaTGeOLH6RJOY6MQ8JuEMMRNM=; b=P8RMJ4+m0h1M9pyYaqSuyDhpQ84481K2piQv67DMHRO8/n++i/HGJVzq9qWEiVtLMi y4pH74l1lZc+GJ/VQ5A8RGrZX7Xvri/Ml34aRmoE7zh7+v740/3fbPUjQTUGECM4RNUO HPV7lcADJPoy+uLLB3QYZQl5K0ldo700cCEOWFSkuMwUw6+Fb6SipBjDoitKXDMoJ0db WDmrH6MH0g/xW1o8AHuU9cGI/MB0Q4Rdz6WYUyflVtMo5AWuvnIY0Z5e0lT+5XnrFEbN piX93VqgVxIUyuCkAvXBwCIbZJ2rkM1nCk1GwZ70m97kfM5SV6ahU6EVl+3MasIA9iuO Nybg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=YVcybWWs; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t128si5359841iof.16.2021.05.10.12.29.33; Mon, 10 May 2021 12:29:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=YVcybWWs; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231410AbhEJT3k (ORCPT + 99 others); Mon, 10 May 2021 15:29:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46716 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231183AbhEJT3j (ORCPT ); Mon, 10 May 2021 15:29:39 -0400 Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 122A2C06175F for ; Mon, 10 May 2021 12:28:34 -0700 (PDT) Received: by mail-pj1-x102c.google.com with SMTP id b14-20020a17090a6e0eb0290155c7f6a356so65684pjk.0 for ; Mon, 10 May 2021 12:28:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=M6r3DxlNPkhf3OhaNDcaTGeOLH6RJOY6MQ8JuEMMRNM=; b=YVcybWWsu7oECIEqY0eEpQTKr6s6lwa3FSiHPeDPAK2x9lqLcMQHbkxX4J2SYORT5L 4qFl61PaPMXY5VNonjTPU0olAfYur8XLRxytz2Enww7aHEdpvtfhot62LymVipbXRQev QBdD+TxtQXT+wgwxwWLwDpdORhRskJfZxT7gqRbfSXGNDsDIpwR3H+ySgHdcMcpPMsPR OlMlIGxZ1GqNwptG16p+mp5AN9XJp/1AF0fFYWwiMVN7SjXtJqMj2n6la/8Irw4XSK0y JugyKoO1onEPUsm1K4rqswIse+jtB4TzSzdwbyaxzbcCE3sM1hjJQXYZLpvII1xdrFrn l+nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=M6r3DxlNPkhf3OhaNDcaTGeOLH6RJOY6MQ8JuEMMRNM=; b=rr8DUYcvMefwtIajG8JtIPWxk/bc0yWwmgiGwp+o8XQviuUYyRGBKu475gl6mNTpar Lq36/7W6n+WeTS6wi0m7fhKHWOLdkIkR+kOxKkVx3vRglwEuGW7fqMH8Q6wXAKuXNDZ4 +9lnlxk+qzHIxBqkeTNdKMqPV7hPY61mGiSdYeo9wSJCqXXWfyiv19G1HQIt8c8D1rAa e7Efo1SUQUrB1xNVmOpd4fdQqVysgBGtSK0u9BPbu/xahjRDHwDoRzOC48vVO+vsfvDm y9W1pq4nUwUqBFzE/lVrknEUB3wGsAtk7sBdsAVOqbQ9vY69n6Vg06s93fnZXpr+7L/t 4nUw== X-Gm-Message-State: AOAM531AyEJzE5oOEMtay4CbeXLhhitcrtDx/l1DpIJq/P+6CtnVyQs4 XkQtMsGs1jKVFap3Ak59nXjTHg== X-Received: by 2002:a17:90a:d246:: with SMTP id o6mr29771057pjw.57.1620674913422; Mon, 10 May 2021 12:28:33 -0700 (PDT) Received: from xps15 (S0106889e681aac74.cg.shawcable.net. [68.147.0.187]) by smtp.gmail.com with ESMTPSA id n8sm11649402pgm.7.2021.05.10.12.28.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 May 2021 12:28:32 -0700 (PDT) Date: Mon, 10 May 2021 13:28:30 -0600 From: Mathieu Poirier To: Mauro Carvalho Chehab Cc: Linux Doc Mailing List , Jonathan Corbet , Leo Yan , Mike Leach , Suzuki K Poulose , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 11/53] docs: trace: coresight: coresight-etm4x-reference.rst: avoid using UTF-8 chars Message-ID: <20210510192830.GA7232@xps15> References: <859218d35d495d5d2c2893bf8e6e087394a107a7.1620641727.git.mchehab+huawei@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <859218d35d495d5d2c2893bf8e6e087394a107a7.1620641727.git.mchehab+huawei@kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 10, 2021 at 12:26:23PM +0200, Mauro Carvalho Chehab wrote: > While UTF-8 characters can be used at the Linux documentation, > the best is to use them only when ASCII doesn't offer a good replacement. > So, replace the occurences of the following UTF-8 characters: > > - U+00a0 (' '): NO-BREAK SPACE > - U+2018 ('‘'): LEFT SINGLE QUOTATION MARK > - U+2019 ('’'): RIGHT SINGLE QUOTATION MARK > > Signed-off-by: Mauro Carvalho Chehab Reviewed-by: Mathieu Poirier > --- > .../coresight/coresight-etm4x-reference.rst | 16 ++++++++-------- > 1 file changed, 8 insertions(+), 8 deletions(-) > > diff --git a/Documentation/trace/coresight/coresight-etm4x-reference.rst b/Documentation/trace/coresight/coresight-etm4x-reference.rst > index b64d9a9c79df..e8ddfc144d9a 100644 > --- a/Documentation/trace/coresight/coresight-etm4x-reference.rst > +++ b/Documentation/trace/coresight/coresight-etm4x-reference.rst > @@ -15,14 +15,14 @@ Root: ``/sys/bus/coresight/devices/etm`` > > The following paragraphs explain the association between sysfs files and the > ETMv4 registers that they effect. Note the register names are given without > -the ‘TRC’ prefix. > +the 'TRC' prefix. > > ---- > > :File: ``mode`` (rw) > :Trace Registers: {CONFIGR + others} > :Notes: > - Bit select trace features. See ‘mode’ section below. Bits > + Bit select trace features. See 'mode' section below. Bits > in this will cause equivalent programming of trace config and > other registers to enable the features requested. > > @@ -89,7 +89,7 @@ the ‘TRC’ prefix. > :Notes: > Pair of addresses for a range selected by addr_idx. Include > / exclude according to the optional parameter, or if omitted > - uses the current ‘mode’ setting. Select comparator range in > + uses the current 'mode' setting. Select comparator range in > control register. Error if index is odd value. > > :Depends: ``mode, addr_idx`` > @@ -277,7 +277,7 @@ the ‘TRC’ prefix. > :Trace Registers: VICTLR{23:20} > :Notes: > Program non-secure exception level filters. Set / clear NS > - exception filter bits. Setting ‘1’ excludes trace from the > + exception filter bits. Setting '1' excludes trace from the > exception level. > > :Syntax: > @@ -427,7 +427,7 @@ the ‘TRC’ prefix. > :Syntax: > ``echo idx > vmid_idx`` > > - Where idx <  numvmidc > + Where idx < numvmidc > > ---- > > @@ -628,7 +628,7 @@ the reset parameter:: > > > > -The ‘mode’ sysfs parameter. > +The 'mode' sysfs parameter. > --------------------------- > > This is a bitfield selection parameter that sets the overall trace mode for the > @@ -696,7 +696,7 @@ Bit assignments shown below:- > ETM_MODE_QELEM(val) > > **description:** > - ‘val’ determines level of Q element support enabled if > + 'val' determines level of Q element support enabled if > implemented by the ETM [IDR0] > > > @@ -780,7 +780,7 @@ Bit assignments shown below:- > ---- > > *Note a)* On startup the ETM is programmed to trace the complete address space > -using address range comparator 0. ‘mode’ bits 30 / 31 modify this setting to > +using address range comparator 0. 'mode' bits 30 / 31 modify this setting to > set EL exclude bits for NS state in either user space (EL0) or kernel space > (EL1) in the address range comparator. (the default setting excludes all > secure EL, and NS EL2) > -- > 2.30.2 >