From: Joe Perches <joe@perches.com>
To: Dexuan Cui <decui@microsoft.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Cathy Avery <cavery@redhat.com>,
KY Srinivasan <kys@microsoft.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
Rolf Neugebauer <rolf.neugebauer@docker.com>
Subject: Re: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets
Date: Tue, 05 Jul 2016 02:38:33 -0700 [thread overview]
Message-ID: <1467711513.19760.18.camel@perches.com> (raw)
In-Reply-To: <CO2PR03MB218222BA0DD55CD967ED4F38BF390@CO2PR03MB2182.namprd03.prod.outlook.com>
On Tue, 2016-07-05 at 09:31 +0000, Dexuan Cui wrote:
> > > +/* This is the address fromat of Hyper-V Sockets.
> > format
> I suppose you meant I should change
> /* This is ...
> to
> /*
> * This is ...
> I'll fix this.
No, I just meant fromat should be format
next prev parent reply other threads:[~2016-07-05 9:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 15:58 [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets Dexuan Cui
2016-06-30 16:12 ` Olaf Hering
2016-06-30 16:12 ` Olaf Hering
2016-06-30 16:22 ` Dexuan Cui
2016-06-30 16:22 ` Dexuan Cui
2016-07-01 6:42 ` Olaf Hering
2016-07-01 6:42 ` Olaf Hering
2016-07-05 1:58 ` Dexuan Cui
2016-07-05 1:58 ` Dexuan Cui
2016-07-05 6:27 ` David Miller
2016-07-05 6:46 ` Dexuan Cui
2016-07-05 6:46 ` Dexuan Cui
2016-07-05 6:58 ` David Miller
2016-07-05 6:58 ` David Miller
2016-07-05 8:21 ` Joe Perches
2016-07-05 9:31 ` Dexuan Cui
2016-07-05 9:31 ` Dexuan Cui
2016-07-05 9:38 ` Joe Perches [this message]
2016-07-05 10:46 ` Dexuan Cui
2016-07-05 10:46 ` Dexuan Cui
2016-07-07 16:02 ` Olaf Hering
2016-07-07 16:02 ` Olaf Hering
2016-07-08 7:01 ` Dexuan Cui
2016-07-08 7:01 ` Dexuan Cui
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=1467711513.19760.18.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=cavery@redhat.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=rolf.neugebauer@docker.com \
--cc=vkuznets@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.