From: Vincent Legoll <vincent.legoll@gmail.com>
To: linux-kbuild@vger.kernel.org
Subject: [PATCH RFC] menuconfigification work
Date: Sun, 9 Apr 2017 11:41:51 +0200 [thread overview]
Message-ID: <20170409094152.22268-1-vincent.legoll@gmail.com> (raw)
Hello,
This is a RFC, for making some menus in Kconfig into menuconfigs, so that it is
easier to disable a whole tree of options without even entering the menu.
The rationale is that the people that build their own kernels may want to
disable unused things.
I tried with one of the easy ones (or so I think) PPS.
Did I do it properly ?
I had to change some "if PPS" into "depends", and even add one that was implicit
before, to PPS_GENERATOR_PARPORT.
Is this kind of work wanted ?
Is this acceptable for mainline ?
If yes, I intend to find other candidates and do proper patch submissions, with
the relevant maintainers also included in the review.
Please advise
Thanks
next reply other threads:[~2017-04-09 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 9:41 Vincent Legoll [this message]
2017-04-09 9:41 ` [PATCH] Make PPS a menuconfig to ease disabling it all 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=20170409094152.22268-1-vincent.legoll@gmail.com \
--to=vincent.legoll@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
/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