linux-kernel - [PATCH 22/23] riscv: pmu.rst : A spello fix

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 29 Mar 2021 10:42:58 +0530
From:   Bhaskar Chowdhury <unixbhaskar@...il.com>
To:     corbet@....net, linux-doc@...r.kernel.org
Cc:     Bhaskar Chowdhury <unixbhaskar@...il.com>, rdunlap@...radead.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH 22/23] riscv: pmu.rst : A spello fix

s/resonable/reasonable/

Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
 Documentation/riscv/pmu.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/riscv/pmu.rst b/Documentation/riscv/pmu.rst
index acb216b99c26..fde31b6aa861 100644
--- a/Documentation/riscv/pmu.rst
+++ b/Documentation/riscv/pmu.rst
@@ -168,7 +168,7 @@ counter (event->count), but also updates the left period to the next interrupt
 But the core of perf does not need direct write to counters.  Writing counters
 is hidden behind the abstraction of 1) *pmu->start*, literally start counting so one
 has to set the counter to a good value for the next interrupt; 2) inside the IRQ
-it should set the counter to the same resonable value.
+it should set the counter to the same reasonable value.

 Reading is not a problem in RISC-V but writing would need some effort, since
 counters are not allowed to be written by S-mode.
--
2.26.3