From: "Michael S. Tsirkin" <mst@redhat.com>
To: Izik Eidus <izik.eidus@ravellosystems.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Alex Fishman <alex.fishman@ravellosystems.com>,
Tamir Shomer <tamirs@daynix.com>,
yvugenfi@redhat.com, qemu-devel@nongnu.org,
Yan Vugenfirer <yan@daynix.com>,
Dmitry Fleytman <dmitry@daynix.com>
Subject: Re: [Qemu-devel] [PATCH 7/7 v5] VMXNET3 paravirtualized device implementation Interface type "vmxnet3" added.
Date: Wed, 4 Apr 2012 22:39:18 +0300 [thread overview]
Message-ID: <20120404193918.GD8967@redhat.com> (raw)
In-Reply-To: <4F7C3401.1040104@ravellosystems.com>
On Wed, Apr 04, 2012 at 02:44:01PM +0300, Izik Eidus wrote:
> Hi,
>
> What about this patch?, everything that was asked from Dmitry was
> accomplished...
> What prevent us from progressing with merging this patch?
>
> Thanks.
Off the top of my head: issues with v5:
polluting global namespace, must scope names
appropriately with vmxnet_ VMXNET_ unless they have file scope.
Don't use names with _ followed by an upper case letter
or that star with two underscores. Don't mix underscores and mixed case.
Don't stick any new types in net.c/pci.c - new devices should use -device
not -net. Global stuff like ethernet header size
should move to central place instead of copy paste.
> On 18/03/2012 11:27, Dmitry Fleytman wrote:
> >Signed-off-by: Dmitry Fleytman<dmitry@daynix.com>
> >Signed-off-by: Yan Vugenfirer<yan@daynix.com>
> >---
> > Makefile.objs | 1 +
> > default-configs/pci.mak | 1 +
> > hw/pci.c | 2 +
> > hw/pci.h | 1 +
> > hw/vmxnet3.c | 2454 +++++++++++++++++++++++++++++++++++++++++++++++
> > hw/vmxnet3.h | 757 +++++++++++++++
> > net.c | 2 +-
> > 7 files changed, 3217 insertions(+), 1 deletions(-)
> > create mode 100644 hw/vmxnet3.c
> > create mode 100644 hw/vmxnet3.h
> >
next prev parent reply other threads:[~2012-04-04 19:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 9:26 [Qemu-devel] [PATCH 0/7 v5] VMXNET3 paravirtual NIC device implementation Dmitry Fleytman
2012-03-18 9:26 ` [Qemu-devel] [PATCH 1/7 v5] Adding missing flag VIRTIO_NET_HDR_F_DATA_VALID from Linux kernel source tre Reformatting comments according to checkpatch.pl requirements Dmitry Fleytman
2012-03-18 9:26 ` [Qemu-devel] [PATCH 2/7 v5] Adding utility function net_checksum_add_cont() that allows checksum calculation of scattered data with odd chunk sizes Dmitry Fleytman
2012-03-18 9:26 ` [Qemu-devel] [PATCH 3/7 v5] Adding utility function iov_net_csum_add() for iovec checksum calculation Dmitry Fleytman
2012-03-18 9:26 ` [Qemu-devel] [PATCH 4/7 v5] Header with various utility functions shared by VMWARE SCSI and network devices Dmitry Fleytman
2012-03-18 9:27 ` [Qemu-devel] [PATCH 5/7 v5] Various utility functions used by VMWARE " Dmitry Fleytman
2012-03-18 9:27 ` [Qemu-devel] [PATCH 6/7 v5] Packet abstraction " Dmitry Fleytman
2012-03-18 9:27 ` [Qemu-devel] [PATCH 7/7 v5] VMXNET3 paravirtualized device implementation Interface type "vmxnet3" added Dmitry Fleytman
2012-04-04 11:44 ` Izik Eidus
2012-04-04 19:39 ` Michael S. Tsirkin [this message]
2012-04-05 5:25 ` Gerhard Wiesinger
2012-04-05 8:02 ` Yan Vugenfirer
2012-04-05 19:00 ` Gerhard Wiesinger
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=20120404193918.GD8967@redhat.com \
--to=mst@redhat.com \
--cc=alex.fishman@ravellosystems.com \
--cc=aliguori@us.ibm.com \
--cc=dmitry@daynix.com \
--cc=izik.eidus@ravellosystems.com \
--cc=qemu-devel@nongnu.org \
--cc=tamirs@daynix.com \
--cc=yan@daynix.com \
--cc=yvugenfi@redhat.com \
/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).