[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gpsd-dev] [PATCH 2/4] Minor reformatting
From: |
Sanjeev Gupta |
Subject: |
[gpsd-dev] [PATCH 2/4] Minor reformatting |
Date: |
Mon, 1 Sep 2014 16:48:17 +0800 |
---
www/reliability.html | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/www/reliability.html b/www/reliability.html
index 70dc291..6754eb6 100644
--- a/www/reliability.html
+++ b/www/reliability.html
@@ -88,10 +88,16 @@ often. This makes it actively difficult for random code
changes to
break our device drivers without somebody noticing.</p>
<p>Which isn't to say those drivers can't be wrong, just that the ways
-they can be wrong are constrained to be through either (a) a
-protocol-spec-level misunderstanding of what the driver is supposed to
-be doing, or (b) an implementation bug somewhere in the program's
-state space that is obscure and difficult to reach. Coverity only
+they can be wrong are constrained to be through either
+<ol>
+<li> a protocol-spec-level misunderstanding of what the driver is
+supposed to be doing, or </li>
+<li> an implementation bug somewhere in the program's
+state space that is obscure and difficult to reach. </li>
+</ol>
+</p>
+
+<p>Coverity only
turned up two driver bugs - static buffer overruns in methods for
changing the device's reporting protocol and line speed that escaped
notice because they can't be checked in our test harnesses but only on
--
2.1.0