|
|
@@ -18,7 +18,7 @@
|
|
|
|
|
|
<h2 class='titleHead'>The Linux Kernel Module Programming Guide</h2>
|
|
|
<div class='author'><span class='ecrm-1200'>Peter Jay Salzman, Michael Burian, Ori Pomerantz, Bob Mottram, Jim Huang</span></div><br />
|
|
|
-<div class='date'><span class='ecrm-1200'>November 8, 2021</span></div>
|
|
|
+<div class='date'><span class='ecrm-1200'>November 16, 2021</span></div>
|
|
|
|
|
|
|
|
|
|
|
|
@@ -4433,8 +4433,8 @@ first things that should be implemented. Logging over a netconsole might also be
|
|
|
worth a try.
|
|
|
</p><!-- l. 1562 --><p class='indent'> While you have seen lots of stuff that can be used to aid debugging here, there are
|
|
|
some things to be aware of. Debugging is almost always intrusive. Adding debug code
|
|
|
-can change the situation enough to make the bug seem to dissappear. Thus you
|
|
|
-should try to keep debug code to a minimum and make sure it does not show up in
|
|
|
+can change the situation enough to make the bug seem to disappear. Thus, you
|
|
|
+should keep debug code to a minimum and make sure it does not show up in
|
|
|
production code.
|
|
|
</p><!-- l. 1566 --><p class='noindent'>
|
|
|
</p>
|
jserv