Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

Hello, On Sat, Dec 16, 2017 at 6:51 PM, Stephen Hemminger 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

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

Hello, On Sat, Dec 16, 2017 at 6:51 PM, Stephen Hemminger 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

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Thu, 14 Dec 2017 09:43:48 -0800 Randy Dunlap wrote: > On 12/13/2017 11:51 PM, Greg KH wrote: > > On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote: > >> On Wed, 13 Dec 2017 09:54:19 +0100 > >> Vincent Legoll wrote: > >> >

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Thu, 14 Dec 2017 09:43:48 -0800 Randy Dunlap wrote: > On 12/13/2017 11:51 PM, Greg KH wrote: > > On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote: > >> On Wed, 13 Dec 2017 09:54:19 +0100 > >> Vincent Legoll wrote: > >> > >>> Hello, > >>> > >>> On Sun, Dec 10, 2017 at

[PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

No need to get into the submenu to disable all HYPERV-related config entries. This makes it easier to disable all HYPERV config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not

[PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

No need to get into the submenu to disable all HYPERV-related config entries. This makes it easier to disable all HYPERV config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On 12/13/2017 11:51 PM, Greg KH wrote: > On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote: >> On Wed, 13 Dec 2017 09:54:19 +0100 >> Vincent Legoll wrote: >> >>> Hello, >>> >>> On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger >>>

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On 12/13/2017 11:51 PM, Greg KH wrote: > On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote: >> On Wed, 13 Dec 2017 09:54:19 +0100 >> Vincent Legoll wrote: >> >>> Hello, >>> >>> On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger >>> wrote: Will this break existing configs?

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote: > On Wed, 13 Dec 2017 09:54:19 +0100 > Vincent Legoll wrote: > > > Hello, > > > > On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger > > wrote: > > > Will this break

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Wed, Dec 13, 2017 at 01:23:38PM -0800, Stephen Hemminger wrote: > On Wed, 13 Dec 2017 09:54:19 +0100 > Vincent Legoll wrote: > > > Hello, > > > > On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger > > wrote: > > > Will this break existing configs? > > > > I don't think so. Last time I

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Wed, 13 Dec 2017 09:54:19 +0100 Vincent Legoll wrote: > Hello, > > On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger > wrote: > > Will this break existing configs? > > I don't think so. Last time I did some similar changes, the

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Wed, 13 Dec 2017 09:54:19 +0100 Vincent Legoll wrote: > Hello, > > On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger > 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

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

Hello, On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger 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

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

Hello, On Sun, Dec 10, 2017 at 6:50 AM, Stephen Hemminger 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

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Sat, 9 Dec 2017 16:21:51 +0100 Vincent Legoll wrote: > No need to get into the submenu to disable all HYPERV-related > config entries. > > This makes it easier to disable all HYPERV config options > without entering the submenu. It will also enable one > to see

Re: [PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

On Sat, 9 Dec 2017 16:21:51 +0100 Vincent Legoll wrote: > No need to get into the submenu to disable all HYPERV-related > config entries. > > This makes it easier to disable all HYPERV config options > without entering the submenu. It will also enable one > to see that en/dis-abled state from

[PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

No need to get into the submenu to disable all HYPERV-related config entries. This makes it easier to disable all HYPERV config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not

[PATCH] hyperv: make HYPERV a menuconfig to ease disabling it all

No need to get into the submenu to disable all HYPERV-related config entries. This makes it easier to disable all HYPERV config options without entering the submenu. It will also enable one to see that en/dis-abled state from the outside menu. This is only intended to change menuconfig UI, not