From: David Miller <davem@davemloft.net>
To: asias@redhat.com
Cc: netdev@vger.kernel.org, acking@vmware.com, dtor@vmware.com,
grantr@vmware.com
Subject: Re: [PATCH] VSOCK: Move af_vsock.h and vsock_addr.h to include/net
Date: Wed, 03 Jul 2013 16:46:37 -0700 (PDT) [thread overview]
Message-ID: <20130703.164637.871965819487633272.davem@davemloft.net> (raw)
In-Reply-To: <1372816788-25548-1-git-send-email-asias@redhat.com>
From: Asias He <asias@redhat.com>
Date: Wed, 3 Jul 2013 09:59:48 +0800
> 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>
The merge window is closed and therefore new submissions like this
which are not bug fixes are not appropriate at this time.
Please resubmit this when the net-next tree opens again, which I
will announce here on netdev.
next prev parent reply other threads:[~2013-07-03 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:59 [PATCH] VSOCK: Move af_vsock.h and vsock_addr.h to include/net Asias He
2013-07-03 23:46 ` David Miller [this message]
2013-07-04 0:42 ` Asias He
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=20130703.164637.871965819487633272.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).