[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEwRq=rWb4sL_YbW5psRRUWL8fu47LP18PTA=Kg8Cko+9P4r3g@mail.gmail.com>
Date: Sun, 17 Dec 2017 15:02:33 +0100
From: Vincent Legoll <vincent.legoll@...il.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: Randy Dunlap <rdunlap@...radead.org>, Greg KH <greg@...ah.com>,
devel@...uxdriverproject.org, haiyangz@...rosoft.com,
sthemmin@...rosoft.com,
Linux Kernel ML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all
Hello,
On Sat, Dec 16, 2017 at 6:51 PM, Stephen Hemminger
<stephen@...workplumber.org> wrote:
> It makes sense to organize the config if you dont break old configs.
> It would be more logical to group and treat all para-virtualized guest
> support in same way. Hyper-V should be next to KVM and Xen.
I agree, I can try to work on that too, as it would nicely complement
the menuconfigifcation.
--
Vincent Legoll
Powered by blists - more mailing lists