public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
	sthemmin@microsoft.com, devel@linuxdriverproject.org,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all
Date: Wed, 13 Dec 2017 13:23:38 -0800	[thread overview]
Message-ID: <20171213132338.1efe04a7@xeon-e3> (raw)
In-Reply-To: <CAEwRq=rwmXMsGPizZko2W8TRhnGNk_c2D8YVQwZuCVu=w78t5w@mail.gmail.com>

On Wed, 13 Dec 2017 09:54:19 +0100
Vincent Legoll <vincent.legoll@gmail.com> wrote:

> Hello,
> 
> On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> > Will this break existing configs?  
> 
> I don't think so. Last time I did some similar changes, the kbuild
> test robot found some warnings on some configurations, I hope
> it will find problems (if any) for that series too (this one is not alone,
> I've got a bunch of other similar patches in-flight)
> 
> Thanks

NAK

Let me give a concrete example of how this will break users.

1. Assume user has a working .config file in their kernel build directory
which builds a kernel that works on Hyper-V.

2. Add your patch (or assume it makes into a later version).

3. User then does

$ make oldconfig
scripts/kconfig/conf  --oldconfig Kconfig
*
* Restart config...
*
*
* Microsoft Hyper-V guest support
*
Microsoft Hyper-V guest support (HYPERV_MENU) [N/y] (NEW) 

If they hit return, the default value is not enabling HyperV and they
will then go on to build a kernel that will not boot on your system.

The default MUST be set to Yes.

  reply	other threads:[~2017-12-13 21:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09 15:21 [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all Vincent Legoll
2017-12-10  5:50 ` Stephen Hemminger
2017-12-13  8:54   ` Vincent Legoll
2017-12-13 21:23     ` Stephen Hemminger [this message]
2017-12-14  7:51       ` Greg KH
2017-12-14 17:43         ` Randy Dunlap
2017-12-16 10:07           ` [PATCH,v2] hyperv: make HYPERV a menuconfig to ease disabling it al Vincent Legoll
2017-12-16 10:07             ` [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all Vincent Legoll
2017-12-16 17:51           ` Stephen Hemminger
2017-12-17 14:02             ` Vincent Legoll

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=20171213132338.1efe04a7@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sthemmin@microsoft.com \
    --cc=vincent.legoll@gmail.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