From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [patch] Add PF_IUCV and AF_IUCV.
Date: Fri, 29 Jun 2007 13:20:00 -0000 [thread overview]
Message-ID: <1183123320.28897.16.camel@localhost> (raw)
Hi,
in February this year the support for AF_IUCV sockets has been added
to the linux kernel. It is a protocol used on the z/VM hypervisor to
communicate between virtual machines. The linux version of socket.h
uses 32 as the id for PF_IUCV and AF_IUCV. This patch adds them to
the linux specific socket.h version in glibc as well.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
---
2007-06-29 Martin Schwidefsky <schwidefsky@de.ibm.com>
* sysdeps/unix/sysv/linux/bits/socket.h: Add PF_IUCV and AF_IUCV.
diff -urpN libc/sysdeps/unix/sysv/linux/bits/socket.h libc-iucv/sysdeps/unix/sysv/linux/bits/socket.h
--- libc/sysdeps/unix/sysv/linux/bits/socket.h 2007-05-07 14:16:43.000000000 +0200
+++ libc-iucv/sysdeps/unix/sysv/linux/bits/socket.h 2007-06-29 15:11:26.000000000 +0200
@@ -90,7 +90,8 @@ enum __socket_type
#define PF_PPPOX 24 /* PPPoX sockets. */
#define PF_WANPIPE 25 /* Wanpipe API sockets. */
#define PF_BLUETOOTH 31 /* Bluetooth sockets. */
-#define PF_MAX 32 /* For now.. */
+#define PF_IUCV 32 /* IUCV sockets. */
+#define PF_MAX 33 /* For now.. */
/* Address families. */
#define AF_UNSPEC PF_UNSPEC
@@ -122,6 +123,7 @@ enum __socket_type
#define AF_PPPOX PF_PPPOX
#define AF_WANPIPE PF_WANPIPE
#define AF_BLUETOOTH PF_BLUETOOTH
+#define AF_IUCV PF_IUCV
#define AF_MAX PF_MAX
/* Socket level values. Others are defined in the appropriate headers.
next reply other threads:[~2007-06-29 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 13:20 Martin Schwidefsky [this message]
2007-06-30 17:08 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1183123320.28897.16.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).