From: Varka Bhadram <varkabhadram@gmail.com>
To: Asias He <asias.hejun@gmail.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Subject: Re: [RFC V2 3/7] VSOCK: Introduce virtio-vsock-common.ko
Date: Sat, 05 Jul 2014 09:12:46 +0530 [thread overview]
Message-ID: <53B77436.3050208@gmail.com> (raw)
In-Reply-To: <d6bb5a91b8433b7eec5692756be00e49a587737a.1404529115.git.asias.hejun@gmail.com>
On Saturday 05 July 2014 08:53 AM, Asias He wrote:
> From: Asias He <asias@redhat.com>
>
> This module contains the common code and header files for the following
> virtio-vsock and virtio-vhost kernel modules.
>
> Signed-off-by: Asias He <asias@redhat.com>
> ---
> include/linux/virtio_vsock.h | 207 ++++
> include/uapi/linux/virtio_ids.h | 1 +
> .../uapi/linux/{virtio_ids.h => virtio_vsock.h} | 78 +-
> net/vmw_vsock/virtio_transport_common.c | 1220 ++++++++++++++++++++
> 4 files changed, 1485 insertions(+), 21 deletions(-)
> create mode 100644 include/linux/virtio_vsock.h
> copy include/uapi/linux/{virtio_ids.h => virtio_vsock.h} (50%)
> create mode 100644 net/vmw_vsock/virtio_transport_common.c
>
This patch having coding style problems. Run checkpatch.pl on this.
--
Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-07-05 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 3:23 [RFC V2 0/7] Introduce VM Sockets virtio transport Asias He
2014-07-05 3:23 ` [RFC V2 1/7] VSOCK: Introduce vsock_find_unbound_socket and vsock_bind_dgram_generic Asias He
2014-07-05 3:23 ` [RFC V2 2/7] VSOCK: Add dgram_skb to vsock_sock Asias He
2014-07-05 3:23 ` [RFC V2 3/7] VSOCK: Introduce virtio-vsock-common.ko Asias He
2014-07-05 3:42 ` Varka Bhadram [this message]
2014-07-05 3:23 ` [RFC V2 4/7] VSOCK: Introduce virtio-vsock.ko Asias He
2014-07-05 3:44 ` Varka Bhadram
2014-07-05 3:23 ` [RFC V2 5/7] VSOCK: Introduce vhost-vsock.ko Asias He
2014-07-05 3:23 ` [RFC V2 6/7] VSOCK: Add Makefile and Kconfig Asias He
2014-07-05 3:23 ` [RFC V2 7/7] Disable debug 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=53B77436.3050208@gmail.com \
--to=varkabhadram@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).