From: Dexuan Cui <decui@microsoft.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Paul Bolle <pebolle@tiscali.nl>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"KY Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>
Subject: RE: [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature
Date: Wed, 8 Jul 2015 05:22:21 +0000 [thread overview]
Message-ID: <66e5e135f09943e6af144ca9f7c31c43@SIXPR30MB031.064d.mgd.msft.net> (raw)
In-Reply-To: <20150707105836.GA19818@aepfle.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 729 bytes --]
> -----Original Message-----
> From: Olaf Hering
> Sent: Tuesday, July 7, 2015 18:59
> Subject: Re: [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature
>
> On Tue, Jul 07, Dexuan Cui wrote:
>
> > OK, removing the line seems better than 'default n', though both reproduce
> > the same "# CONFIG_HYPERV_SOCK is not set".
>
> Perhaps "default VMBUS" (or whatever syntax is needed) may be the way to
> enable it conditionally.
>
> Olaf
Thanks, Olaf!
I think we can use "default m if HYPERV".
Paul, I'll remove the sentence "If unsure, say N."
Thanks,
-- Dexuan
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2015-07-08 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 14:47 Dexuan Cui
2015-07-07 9:37 ` Paul Bolle
2015-07-07 10:02 ` Dexuan Cui
2015-07-07 10:10 ` Olaf Hering
2015-07-07 10:20 ` Dexuan Cui
2015-07-07 10:58 ` Olaf Hering
2015-07-08 5:22 ` Dexuan Cui [this message]
2015-07-07 11:51 ` Paul Bolle
2015-07-07 18:31 ` Stephen Hemminger
2015-07-08 3:56 ` 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=66e5e135f09943e6af144ca9f7c31c43@SIXPR30MB031.064d.mgd.msft.net \
--to=decui@microsoft.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=driverdev-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=pebolle@tiscali.nl \
/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®