From: Vincent Legoll <vincent.legoll@gmail.com>
To: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: [PATCH,v2] hyperv: make HYPERV a menuconfig to ease disabling it al
Date: Sat, 16 Dec 2017 11:07:58 +0100 [thread overview]
Message-ID: <20171216100759.10381-1-vincent.legoll@gmail.com> (raw)
In-Reply-To: <b8d654d1-67c9-b6bc-7aad-e5c7a4beec48@infradead.org>
Hello,
The following patch add a "default y" to the menuconfig to avoid breaking
existing configs.
Please advise if this is better, and sufficient.
Tell me if these kind of changes are not welcome in the kernel, so that I
won't continue with other similar work. I am an actual user of menuconfig,
and find it really harder to use than necessary. A lot of new drivers and
config options have been added, with only a few relevant to my HW.
It is getting very hard to go through menuconfig and disable all the
unneeded stuff.
I use distro kernels on some of my HW, but for the smaller armels or i686s,
I actually want to strip the kernel config.
I find the existing menuconfigs a good solution for that problem, because
they allow me to disable huge lists of stuff when I know I don't need them
without even bothering to enter the menu, an go to each one disabling it.
I may not doing it all right, but I think this kind of patch helps at least
some of us. Please advise if there's a better way.
Thanks
next prev parent reply other threads:[~2017-12-16 10:08 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
2017-12-14 7:51 ` Greg KH
2017-12-14 17:43 ` Randy Dunlap
2017-12-16 10:07 ` Vincent Legoll [this message]
2017-12-16 10:07 ` 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=20171216100759.10381-1-vincent.legoll@gmail.com \
--to=vincent.legoll@gmail.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sthemmin@microsoft.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
all inboxes | Powered by JetHome®