From: David Miller <davem@davemloft.net>
To: acking@vmware.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, pv-drivers@vmware.com,
kraxel@redhat.com
Subject: Re: [PATCH 0/4] Minor vSockets fixes
Date: Mon, 18 Feb 2013 15:03:08 -0500 (EST) [thread overview]
Message-ID: <20130218.150308.1936873338532880021.davem@davemloft.net> (raw)
In-Reply-To: <1361203453-1347-1-git-send-email-acking@vmware.com>
From: Andy King <acking@vmware.com>
Date: Mon, 18 Feb 2013 08:04:09 -0800
> Minor vSockets fixes, two of which were reported on LKML.
Series applied, thanks.
prev parent reply other threads:[~2013-02-18 20:03 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 ` [PATCH 3/4] VSOCK: Remove hypervisor-only socket option Andy King
2013-02-18 16:04 ` [PATCH 4/4] VSOCK: Don't reject PF_VSOCK protocol Andy King
2013-02-18 20:03 ` David Miller [this message]
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=20130218.150308.1936873338532880021.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acking@vmware.com \
--cc=kraxel@redhat.com \
--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).