netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Dexuan Cui <decui@microsoft.com>, Olaf Hering <olaf@aepfle.de>
Cc: "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: Tue, 07 Jul 2015 13:51:21 +0200	[thread overview]
Message-ID: <1436269881.20057.139.camel@tiscali.nl> (raw)
In-Reply-To: <cf30a808b461480d8c399e556ddef513@SIXPR30MB031.064d.mgd.msft.net>

On di, 2015-07-07 at 10:20 +0000, Dexuan Cui wrote:
> OK, removing the line seems better than 'default n', though both 
> reproduce the same "# CONFIG_HYPERV_SOCK is not set".

Speaking from memory (so chances are I'm forgetting some silly detail)
that is because
    # CONFIG_FOO is not set

will be printed if FOO's dependencies are met and FOO either has a
"prompt" or a default of 'n'.

Hope this helps,


Paul Bolle

  parent reply	other threads:[~2015-07-07 11:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 14:47 [PATCH 6/7] hvsock: introduce Hyper-V VM Sockets feature 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
2015-07-07 11:51       ` Paul Bolle [this message]
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=1436269881.20057.139.camel@tiscali.nl \
    --to=pebolle@tiscali.nl \
    --cc=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --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 \
    /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).