From: David Miller <davem@davemloft.net>
To: acking@vmware.com
Cc: asias@redhat.com, netdev@vger.kernel.org, dtor@vmware.com,
grantr@vmware.com
Subject: Re: [PATCH net-next] VSOCK: Move af_vsock.h and vsock_addr.h to include/net
Date: Sat, 27 Jul 2013 22:14:20 -0700 (PDT) [thread overview]
Message-ID: <20130727.221420.1069834348574740989.davem@davemloft.net> (raw)
In-Reply-To: <728438598.12051834.1374853298283.JavaMail.root@vmware.com>
From: Andy King <acking@vmware.com>
Date: Fri, 26 Jul 2013 08:41:38 -0700 (PDT)
>> This is useful for other VSOCK transport implemented outside the
>> net/vmw_vsock/ directory to use these headers.
>>
>> Signed-off-by: Asias He <asias@redhat.com>
>
> Acked-by: Andy King <acking@vmware.com>
Applied, thanks.
prev parent reply other threads:[~2013-07-28 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 9:39 [PATCH net-next] VSOCK: Move af_vsock.h and vsock_addr.h to include/net Asias He
2013-07-26 15:41 ` Andy King
2013-07-28 5:14 ` 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=20130727.221420.1069834348574740989.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=acking@vmware.com \
--cc=asias@redhat.com \
--cc=dtor@vmware.com \
--cc=grantr@vmware.com \
--cc=netdev@vger.kernel.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).