Following movement of functions from uipc_socket2.c to uipc_socket.c and

uipc_sockbuf.c, clean up and update comments.

1 files changed, 7 insertions, 6 deletions

diff --git a/sys/kern/uipc_sockbuf.c b/sys/kern/uipc_sockbuf.c
index 2293eef..381632c 100644
--- a/sys/kern/uipc_sockbuf.c
+++ b/sys/kern/uipc_sockbuf.c
@@ -980,8 +980,8 @@ sbdroprecord(struct sockbuf *sb)
 }
 
 /*
- * Create a "control" mbuf containing the specified data
- * with the specified type for presentation on a socket buffer.
+ * Create a "control" mbuf containing the specified data with the specified
+ * type for presentation on a socket buffer.
  */
 struct mbuf *
 sbcreatecontrol(p, size, type, level)
@@ -1014,10 +1014,11 @@ sbcreatecontrol(p, size, type, level)
 }
 
 /*
- * This does the same for sockbufs.  Note that the xsockbuf structure,
- * since it is always embedded in a socket, does not include a self
- * pointer nor a length.  We make this entry point public in case
- * some other mechanism needs it.
+ * This does the same for socket buffers that sotoxsocket does for sockets:
+ * generate an user-format data structure describing the socket buffer.  Note
+ * that the xsockbuf structure, since it is always embedded in a socket, does
+ * not include a self pointer nor a length.  We make this entry point public
+ * in case some other mechanism needs it.
  */
 void
 sbtoxsockbuf(struct sockbuf *sb, struct xsockbuf *xsb)