Reduce network stack oddness: implement .pru_sockaddr and .pru_peeraddr

protocol entry points using functions named proto_getsockaddr and
proto_getpeeraddr rather than proto_setsockaddr and proto_setpeeraddr.
While it's true that sockaddrs are allocated and set, the net effect is
to retrieve (get) the socket address or peer address from a socket, not
set it, so align names to that intent.

1 files changed, 2 insertions, 2 deletions

diff --git a/sys/netipx/ipx_usrreq.c b/sys/netipx/ipx_usrreq.c
index 2ee7e94..ad60f4b 100644
--- a/sys/netipx/ipx_usrreq.c
+++ b/sys/netipx/ipx_usrreq.c
@@ -586,7 +586,7 @@ ipx_peeraddr(so, nam)
 	struct ipxpcb *ipxp = sotoipxpcb(so);
 
 	KASSERT(ipxp != NULL, ("ipx_peeraddr: ipxp == NULL"));
-	ipx_setpeeraddr(ipxp, nam);
+	ipx_getpeeraddr(ipxp, nam);
 	return (0);
 }
 
@@ -671,7 +671,7 @@ ipx_sockaddr(so, nam)
 	struct ipxpcb *ipxp = sotoipxpcb(so);
 
 	KASSERT(ipxp != NULL, ("ipx_sockaddr: ipxp == NULL"));
-	ipx_setsockaddr(ipxp, nam);
+	ipx_getsockaddr(ipxp, nam);
 	return (0);
 }