[src/pgoyette-compat]: src/doc Now that the rtsock_50 stuff has been disentan...

[pgoyette <pgoyette%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/9b0f4b2d6153
branches:  pgoyette-compat
changeset: 447553:9b0f4b2d6153
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Tue Jan 15 22:06:34 2019 +0000

description:
Now that the rtsock_50 stuff has been disentangled, remove a reference
to that in another entry.

diffstat:

 doc/TODO.compat-module |  10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)

diffs (24 lines):

diff -r cea4cb82b6f2 -r 9b0f4b2d6153 doc/TODO.compat-module
--- a/doc/TODO.compat-module    Tue Jan 15 22:01:26 2019 +0000
+++ b/doc/TODO.compat-module    Tue Jan 15 22:06:34 2019 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.compat-module,v 1.1.2.22 2019/01/15 03:44:06 pgoyette Exp $ */
+/* $NetBSD: TODO.compat-module,v 1.1.2.23 2019/01/15 22:06:34 pgoyette Exp $ */
 
 DONE
 ----
@@ -92,10 +92,10 @@
     into the monolithic COMPAT module on HEAD.  Thus, its absence from
     any of the version-specific modules is not a regression.
 
-20. For compat_50, in addition to rtsock there are some things in dev/gpio
-    and dev/wscons/wsmux that I haven't been able to cleanly separate.
-    These items are not currently included in the monolithic COMPAT module
-    on HEAD, so lack of integration on the branch is not a regression.
+20. For compat_50, there are some things in dev/gpio and dev/wscons/wsmux
+    that I haven't been able to cleanly separate.  These items are not
+    currently included in the monolithic COMPAT module on HEAD, so lack of
+    integration on the branch is not a regression.
 
 21. Find all the remaining dependencies on the compat_utils routines and
     deal with them appropriately.  For now, we simply ensure that they