From: Greg KH <gregkh@linuxfoundation.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: arve@android.com, riandrews@android.com,
devel@driverdev.osuosl.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make ANDROID a menuconfig to ease disabling it all
Date: Fri, 14 Apr 2017 14:32:26 +0200 [thread overview]
Message-ID: <20170414123226.GB17217@kroah.com> (raw)
In-Reply-To: <CAEwRq=q+wxxxcNkij7ALj3rYN8ir0sH9mLtkaVLkSnZzUaEafQ@mail.gmail.com>
On Fri, Apr 14, 2017 at 11:46:07AM +0200, Vincent Legoll wrote:
> Hello,
>
> >> No need to get into the submenu to disable all ANDROID-related config entries
> >
> > I don't understand this, what exactly do you mean?
>
> This is intended for people using make menuconfig to tailor
> their kernel config to their need by disabling all options they
> don't need. In order to have a smaller kernel, for example,
> but also to get smaller build times.
That's fine, but you aren't actually changing the functionality of any
of the build options here. You are just adding a 'menu' and showing
things a bit differently. You aren't changing any dependancies (which
is what dictates what is and is not built), which does not make it
easier, or harder, to disable/enable anything here.
I'm not against this, but you need to explain it a lot better as to what
you are doing and why. The "why" isn't covered by the "this will make
the kernel build smaller", as that's just not true :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-04-14 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 9:04 Vincent Legoll
2017-04-14 9:27 ` Greg KH
2017-04-14 9:46 ` Vincent Legoll
2017-04-14 12:32 ` Greg KH [this message]
2017-04-14 12:46 ` Vincent Legoll
2017-12-03 18:33 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=20170414123226.GB17217@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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
all inboxes | Powered by JetHome®