Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: decui@microsoft.com
Cc: mkubecek@suse.cz, jasowang@redhat.com, georgezhang@vmware.com,
	sthemmin@microsoft.com, rolf.neugebauer@docker.com,
	marcelo.cerri@canonical.com, asias@redhat.com,
	dan.carpenter@oracle.com, olaf@aepfle.de, haiyangz@microsoft.com,
	dave.scott@docker.com, stefanha@redhat.com, apw@canonical.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, joe@perches.com,
	devel@linuxdriverproject.org, vkuznets@redhat.com,
	jhansen@vmware.com
Subject: Re: [PATCH net-next 1/3] VMCI: only load on VMware hypervisor
Date: Wed, 16 Aug 2017 11:54:16 -0700 (PDT)	[thread overview]
Message-ID: <20170816.115416.1591353514541788122.davem@davemloft.net> (raw)
In-Reply-To: <KL1P15301MB0008FB89237C3BB7A6D2BB39BF820@KL1P15301MB0008.APCP153.PROD.OUTLOOK.COM>

From: Dexuan Cui <decui@microsoft.com>
Date: Wed, 16 Aug 2017 18:51:36 +0000

> It looks typically modern Linux distros have CONFIG_HYPERVISOR_GUEST=y
> by default

It doesn't matter what any distribution does or does not do.

People are going to do 'randconfig' builds over thousands and
thousands of configuration combinations to test your changes,
and those tests will fail.

> Do you want me to submit a v2 for this patch with the Kconfig change?

Of course, there is no way I can apply your series as-is.

  reply	other threads:[~2017-08-16 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 22:13 [PATCH net-next 1/3] VMCI: only load on VMware hypervisor Dexuan Cui
2017-08-16 18:06 ` David Miller
2017-08-16 18:51   ` Dexuan Cui
2017-08-16 18:54     ` David Miller [this message]
2017-08-16 19:44 ` Jorgen S. Hansen
2017-08-16 22:33   ` Dexuan Cui
2017-08-17  8:10     ` 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=20170816.115416.1591353514541788122.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=apw@canonical.com \
    --cc=asias@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dave.scott@docker.com \
    --cc=decui@microsoft.com \
    --cc=devel@linuxdriverproject.org \
    --cc=georgezhang@vmware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=jhansen@vmware.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.cerri@canonical.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=rolf.neugebauer@docker.com \
    --cc=stefanha@redhat.com \
    --cc=sthemmin@microsoft.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