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@vger.kernel.org
Subject: Re: [PATCH] Make ANDROID a menuconfig to ease disabling it all
Date: Fri, 14 Apr 2017 11:27:05 +0200 [thread overview]
Message-ID: <20170414092705.GA1944@kroah.com> (raw)
In-Reply-To: <20170414090421.4281-1-vincent.legoll@gmail.com>
On Fri, Apr 14, 2017 at 11:04:21AM +0200, Vincent Legoll wrote:
> No need to get into the submenu to disable all ANDROID-related config entries
I don't understand this, what exactly do you mean?
>
> Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
> ---
> drivers/android/Kconfig | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/android/Kconfig b/drivers/android/Kconfig
> index a82fc02..c2b6c37 100644
> --- a/drivers/android/Kconfig
> +++ b/drivers/android/Kconfig
> @@ -1,15 +1,11 @@
> -menu "Android"
> -
> -config ANDROID
> +menuconfig ANDROID
> bool "Android Drivers"
> ---help---
> Enable support for various drivers needed on the Android platform
>
> -if ANDROID
> -
> config ANDROID_BINDER_IPC
> bool "Android Binder IPC Driver"
> - depends on MMU
> + depends on ANDROID && MMU
> default n
> ---help---
> Binder is used in Android for both communication between processes,
> @@ -43,7 +39,3 @@ config ANDROID_BINDER_IPC_32BIT
> earlier).
>
> Note that enabling this will break newer Android user-space.
> -
> -endif # if ANDROID
> -
> -endmenu
There are other ANDROID config options in the kernel other than right
here, so having a "menu" is a bit odd, right?
thanks,
greg k-h
next prev parent reply other threads:[~2017-04-14 9:27 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 [this message]
2017-04-14 9:46 ` Vincent Legoll
2017-04-14 12:32 ` Greg KH
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=20170414092705.GA1944@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®