From: Andy King <acking@vmware.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Cc: pv-drivers@vmware.com, Andy King <acking@vmware.com>,
davem@davemloft.net
Subject: [PATCH 3/4] VSOCK: Remove hypervisor-only socket option
Date: Mon, 18 Feb 2013 08:04:12 -0800 [thread overview]
Message-ID: <1361203453-1347-4-git-send-email-acking@vmware.com> (raw)
In-Reply-To: <1361203453-1347-1-git-send-email-acking@vmware.com>
Remove hypervisor-only socket option.
Reported-by: Gerd Hoffmann <kraxel@redhat.com>
Acked-by: Dmitry Torokhov <dtor@vmware.com>
Signed-off-by: Andy King <acking@vmware.com>
---
include/uapi/linux/vm_sockets.h | 8 --------
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/include/uapi/linux/vm_sockets.h b/include/uapi/linux/vm_sockets.h
index f7f2e99..df91301 100644
--- a/include/uapi/linux/vm_sockets.h
+++ b/include/uapi/linux/vm_sockets.h
@@ -52,14 +52,6 @@
#define SO_VM_SOCKETS_PEER_HOST_VM_ID 3
-/* Option name for socket's service label. Use as the option name in
- * setsockopt(3) or getsockopt(3) to set or get the service label for a socket.
- * The service label is a C-style NUL-terminated string. Only available for
- * hypervisor endpoints.
- */
-
-#define SO_VM_SOCKETS_SERVICE_LABEL 4
-
/* Option name for determining if a socket is trusted. Use as the option name
* in getsockopt(3) to determine if a socket is trusted. The value is a
* signed integer.
--
1.7.4.1
next prev parent reply other threads:[~2013-02-18 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 16:04 [PATCH 0/4] Minor vSockets fixes Andy King
2013-02-18 16:04 ` [PATCH 1/4] VSOCK: get rid of EXPORT_SYMTAB Andy King
2013-02-18 16:04 ` [PATCH 2/4] VSOCK: get rid of vsock_version.h Andy King
2013-02-18 16:04 ` Andy King [this message]
2013-02-18 16:04 ` [PATCH 4/4] VSOCK: Don't reject PF_VSOCK protocol Andy King
2013-02-18 20:03 ` [PATCH 0/4] Minor vSockets fixes David Miller
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=1361203453-1347-4-git-send-email-acking@vmware.com \
--to=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pv-drivers@vmware.com \
--cc=virtualization@lists.linux-foundation.org \
/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 NNTP newsgroup(s).