From: Rob Herring <robh@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2 13/24] docs: arm64: convert perf.txt to ReST format
Date: Tue, 2 Jun 2020 15:01:22 -0600 [thread overview]
Message-ID: <20200602210122.GA3930090@bogus> (raw)
In-Reply-To: <e000ccaf21f899a4c503c0a0e8734a2a3e177ee6.1581956285.git.mchehab+huawei@kernel.org>
On Mon, Feb 17, 2020 at 05:20:31PM +0100, Mauro Carvalho Chehab wrote:
> This file is almost in ReST. All it needs is a rename and
> adding a :field: for the two fields at the beginning
> (author and date).
>
> While here, add a proper SPDX header, and use the standard
> markup for document titles, just for consistency.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/arm64/index.rst | 1 +
> Documentation/arm64/{perf.txt => perf.rst} | 7 +++++--
> 2 files changed, 6 insertions(+), 2 deletions(-)
> rename Documentation/arm64/{perf.txt => perf.rst} (95%)
Is there some reason this hasn't been merged or commented on?
> diff --git a/Documentation/arm64/index.rst b/Documentation/arm64/index.rst
> index 5c0c69dc58aa..c51d0fa80318 100644
> --- a/Documentation/arm64/index.rst
> +++ b/Documentation/arm64/index.rst
> @@ -13,6 +13,7 @@ ARM64 Architecture
> hugetlbpage
> legacy_instructions
> memory
> + perf
> pointer-authentication
> silicon-errata
> sve
> diff --git a/Documentation/arm64/perf.txt b/Documentation/arm64/perf.rst
> similarity index 95%
> rename from Documentation/arm64/perf.txt
> rename to Documentation/arm64/perf.rst
> index 0d6a7d87d49e..9c76a97baf28 100644
> --- a/Documentation/arm64/perf.txt
> +++ b/Documentation/arm64/perf.rst
> @@ -1,8 +1,11 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +=====================
> Perf Event Attributes
> =====================
>
> -Author: Andrew Murray <andrew.murray@arm.com>
> -Date: 2019-03-06
> +:Author: Andrew Murray <andrew.murray@arm.com>
> +:Date: 2019-03-06
Andrew is no long with Arm. Both lines look like things that become
stale, so I'd just remove them.
Rob
next prev parent reply other threads:[~2020-06-02 21:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:20 [PATCH v2 00/24] Manually convert thermal, crypto and misc devices to ReST Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 01/24] docs: thermal: convert cpu-idle-cooling.rst " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 02/24] docs: crypto: convert asymmetric-keys.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 03/24] docs: crypto: convert api-intro.txt to ReST format Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 04/24] docs: crypto: convert async-tx-api.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 05/24] docs: crypto: descore-readme.txt: convert " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 06/24] docs: misc-devices/spear-pcie-gadget.txt: convert to ReST Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 07/24] docs: misc-devices/pci-endpoint-test.txt: " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 08/24] " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 09/24] docs: misc-devices/c2port.txt: convert to ReST format Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 10/24] docs: misc-devices/bh1770glc.txt: convert to ReST Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 11/24] docs: misc-devices/apds990x.txt: convert to ReST format Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 12/24] docs: pci: endpoint/function/binding/pci-test.txt convert to ReST Mauro Carvalho Chehab
2020-02-27 23:03 ` Bjorn Helgaas
2020-02-17 16:20 ` [PATCH v2 13/24] docs: arm64: convert perf.txt to ReST format Mauro Carvalho Chehab
2020-06-02 21:01 ` Rob Herring [this message]
2020-02-17 16:20 ` [PATCH v2 14/24] docs: cpu-freq: convert index.txt to ReST Mauro Carvalho Chehab
2020-02-17 20:06 ` Rafael J. Wysocki
2020-02-28 9:14 ` Mauro Carvalho Chehab
2020-02-28 9:33 ` Rafael J. Wysocki
2020-03-02 21:19 ` Jonathan Corbet
2020-03-02 22:16 ` Rafael J. Wysocki
2020-03-03 13:54 ` Mauro Carvalho Chehab
2020-03-03 14:01 ` Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 15/24] docs: cpu-freq: convert amd-powernow.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 16/24] docs: cpu-freq: convert core.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 17/24] docs: cpu-freq: convert cpu-drivers.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 18/24] docs: cpu-freq: convert cpufreq-nforce2.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 19/24] docs: cpu-freq: convert cpufreq-stats.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 20/24] docs: cpu-freq: convert pcc-cpufreq.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 21/24] docs: powerpc: convert vcpudispatch_stats.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 22/24] docs: sh: convert new-machine.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 23/24] docs: sh: convert register-banks.txt " Mauro Carvalho Chehab
2020-02-17 16:20 ` [PATCH v2 24/24] docs: trace: ring-buffer-design.txt: convert to ReST format Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200602210122.GA3930090@bogus \
--to=robh@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).