[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20210316044424.3068802-1-unixbhaskar@gmail.com>
Date: Tue, 16 Mar 2021 10:14:24 +0530
From: Bhaskar Chowdhury <unixbhaskar@...il.com>
To: pbonzini@...hat.com, corbet@....net, kvm@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: rdunlap@...radead.org, Bhaskar Chowdhury <unixbhaskar@...il.com>
Subject: [PATCH] docs: virt: kvm: Trivial typo fix in the file timekeeping.rst
s/extremal/external/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
---
But...Paolo,is it also "extreme"? I am in a catch-22?
Documentation/virt/kvm/timekeeping.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/timekeeping.rst b/Documentation/virt/kvm/timekeeping.rst
index 21ae7efa29ba..932d7f7d1ece 100644
--- a/Documentation/virt/kvm/timekeeping.rst
+++ b/Documentation/virt/kvm/timekeeping.rst
@@ -299,7 +299,7 @@ device.
The HPET spec is rather loose and vague, requiring at least 3 hardware timers,
but allowing implementation freedom to support many more. It also imposes no
-fixed rate on the timer frequency, but does impose some extremal values on
+fixed rate on the timer frequency, but does impose some external values on
frequency, error and slew.
In general, the HPET is recommended as a high precision (compared to PIT /RTC)
--
2.30.2
Powered by blists - more mailing lists