[src/trunk]: src/doc Note that the xen vs non-xen issue has been resolved by ...

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

details:   https://anonhg.NetBSD.org/src/rev/e06ccd24a248
branches:  trunk
changeset: 935542:e06ccd24a248
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Sun Jul 05 02:04:25 2020 +0000

description:
Note that the xen vs non-xen issue has been resolved by recent commit
from Chuck Silvers.  (Also add xref to PR port-xen/53130 for history.)

diffstat:

 doc/TODO.modules |  9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)

diffs (21 lines):

diff -r 6032666a09d2 -r e06ccd24a248 doc/TODO.modules
--- a/doc/TODO.modules  Sun Jul 05 01:09:48 2020 +0000
+++ b/doc/TODO.modules  Sun Jul 05 02:04:25 2020 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.modules,v 1.21 2019/12/08 15:51:49 pgoyette Exp $ */
+/* $NetBSD: TODO.modules,v 1.22 2020/07/05 02:04:25 pgoyette Exp $ */
 
 Some notes on the limitations of our current (as of 7.99.35) module
 subsystem.  This list was triggered by an Email exchange between
@@ -233,6 +233,9 @@
     building xen-variant modules (on amd4, and likely i386).  In some
     cases, wrong headers are included (because a XEN-related #define
     is missing), but even if you add the definition some headers get
-    included in the wrong order.  On particular fallout from this is
+    included in the wrong order.  One particular fallout from this is
     the inability to have a compat version of x86_64 cpu-microcode
-    module.
+    module.  PR port-xen/53130
+
+    This is likely to be fixed by Chuck Silvers on 2020-07-04 which
+    removed the differences between the xen and non-xen module ABIs.