From: David Miller <davem@davemloft.net>
To: decui@microsoft.com
Cc: olaf@aepfle.de, rolf.neugebauer@docker.com, jasowang@redhat.com,
linux-kernel@vger.kernel.org, joe@perches.com,
netdev@vger.kernel.org, gregkh@linuxfoundation.org,
apw@canonical.com, devel@linuxdriverproject.org,
vkuznets@redhat.com, haiyangz@microsoft.com
Subject: Re: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets
Date: Mon, 04 Jul 2016 23:58:53 -0700 (PDT) [thread overview]
Message-ID: <20160704.235853.711410488074031899.davem@davemloft.net> (raw)
In-Reply-To: <CO2PR03MB21821C4832602D8464D9C092BF390@CO2PR03MB2182.namprd03.prod.outlook.com>
From: Dexuan Cui <decui@microsoft.com>
Date: Tue, 5 Jul 2016 06:46:24 +0000
>> From: David Miller [mailto:davem@davemloft.net]
>> Sent: Tuesday, July 5, 2016 14:27
>> To: Dexuan Cui <decui@microsoft.com>
>> Subject: Re: [PATCH v14 net-next 1/1] hv_sock: introduce Hyper-V Sockets
>>
>> From: Dexuan Cui <decui@microsoft.com>
>> Date: Tue, 5 Jul 2016 01:58:31 +0000
>>
>> > Not sure if you had a chance to review this version.
>>
>> Why me?
> I just think you're the most responsive reviewer. :-)
I'm the only reviewer, and that's a problem and simply unacceptable.
Nobody other than me is reviewing this code, and I'm not applying
these changes while that is the case.
next prev parent reply other threads:[~2016-07-05 6:58 UTC|newest]
Thread overview: 14+ 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:22 ` Dexuan Cui
2016-07-01 6:42 ` Olaf Hering
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:58 ` David Miller [this message]
2016-07-05 8:21 ` Joe Perches
2016-07-05 9:31 ` Dexuan Cui
2016-07-05 9:38 ` Joe Perches
2016-07-05 10:46 ` Dexuan Cui
2016-07-07 16:02 ` Olaf Hering
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=20160704.235853.711410488074031899.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=apw@canonical.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=joe@perches.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 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).