From: Dmitry Torokhov <dtor@vmware.com>
To: pv-drivers@vmware.com
Cc: David Miller <davem@davemloft.net>,
gregkh@linuxfoundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Pv-drivers] [PATCH 0/6] VSOCK for Linux upstreaming
Date: Tue, 08 Jan 2013 17:41:44 -0800 [thread overview]
Message-ID: <1683801.VNKd61ZM1Q@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20130108.173056.1029788106028104571.davem@davemloft.net>
On Tuesday, January 08, 2013 05:30:56 PM David Miller wrote:
> From: Greg KH <gregkh@linuxfoundation.org>
> Date: Tue, 8 Jan 2013 16:21:10 -0800
>
> > On Tue, Jan 08, 2013 at 03:59:08PM -0800, George Zhang wrote:
> >> * * *
> >>
> >> This series of VSOCK linux upstreaming patches include latest udpate from
> >> VMware to address Greg's and all other's code review comments.
> >
> > Dave, you acked these patches a while ago,
>
> Really? I'd like to see where I did that.
>
> Instead, what I remember doing was deferring to the feedback these
> folks received, stating that ideas that the virtio people had
> mentioned should be considered instead.
>
> http://marc.info/?l=linux-netdev&m=135301515818462&w=2
I believe Andy replied to Anthony's AF_VMCHANNEL post and the differences
between the proposed solutions.
>
> So definitely NACK this code and any infrastructure you've
> merged which essentialy depends upon it.
No, there is no infrastructure that depends on VSOCK, as VSOCK is built
on top of VMCI, not the other way around.
Thanks,
Dmitry
next prev parent reply other threads:[~2013-01-09 1:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 23:59 George Zhang
2013-01-08 23:59 ` [PATCH 1/6] VSOCK: vsock protocol implementation George Zhang
2013-01-08 23:59 ` [PATCH 2/6] VSOCK: vsock address implementaion George Zhang
2013-01-08 23:59 ` [PATCH 3/6] VSOCK: notification implementation George Zhang
2013-01-09 0:00 ` [PATCH 4/6] VSOCK: statistics implementation George Zhang
2013-01-09 0:00 ` [PATCH 5/6] VSOCK: utility functions George Zhang
2013-01-09 0:00 ` [PATCH 6/6] VSOCK: header and config files George Zhang
2013-01-09 0:21 ` [PATCH 0/6] VSOCK for Linux upstreaming Greg KH
2013-01-09 1:30 ` David Miller
2013-01-09 1:41 ` Dmitry Torokhov [this message]
2013-01-09 1:46 ` [Pv-drivers] " David Miller
2013-01-09 2:22 ` Dmitry Torokhov
2013-01-09 8:10 ` Gerd Hoffmann
2013-01-10 2:42 ` Andy King
2013-01-25 21:33 ` Andy King
2013-02-05 4:42 ` Andy King
-- strict thread matches above, loose matches on Subject: below --
2012-11-11 21:59 Sasha Levin
2012-11-14 16:42 ` [Pv-drivers] " Andy King
2012-11-05 18:09 David Miller
2012-11-05 18:19 ` [Pv-drivers] " Andy King
2012-11-07 6:58 ` Gerd Hoffmann
2012-11-08 15:47 ` Andy King
2012-11-15 21:32 ` Anthony Liguori
2012-11-19 9:59 ` Benjamin Herrenschmidt
2012-12-06 15:28 ` Andy King
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=1683801.VNKd61ZM1Q@dtor-d630.eng.vmware.com \
--to=dtor@vmware.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®