From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] binder: let ANDROID_BINDER_IPC_32BIT be selectable on 32bit ARM
Date: Tue, 8 Aug 2017 19:03:05 +0800 [thread overview]
Message-ID: <20170808110305.2748-1-jszhang@marvell.com> (raw)
As noted in commit d0bdff0db809 ("staging: Fix build issues with new
binder API"), we can add back the choice for 32bit ARM "once a 64bit
__get_user_asm_* implementation is merged." Commit e38361d032f1 ("ARM:
8091/2: add get_user() support for 8 byte types") has added the
support, so it's time to let ANDROID_BINDER_IPC_32BIT be selectable on
32bit ARM
Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
---
drivers/android/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/android/Kconfig b/drivers/android/Kconfig
index 832e885349b1..aca5dc30b97b 100644
--- a/drivers/android/Kconfig
+++ b/drivers/android/Kconfig
@@ -32,7 +32,7 @@ config ANDROID_BINDER_DEVICES
therefore logically separated from the other devices.
config ANDROID_BINDER_IPC_32BIT
- bool
+ bool "Use old (Android 4.4 and earlier) 32-bit binder API"
depends on !64BIT && ANDROID_BINDER_IPC
default y
---help---
--
2.14.0
next reply other threads:[~2017-08-08 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 11:03 Jisheng Zhang [this message]
2017-08-23 1:51 ` [PATCH] binder: let ANDROID_BINDER_IPC_32BIT be selectable on 32bit ARM Greg KH
2017-08-23 2:34 ` Jisheng Zhang
2017-08-23 2:56 ` John Stultz
2017-08-23 2:56 ` [EXT] " Jisheng Zhang
2017-08-23 2:57 ` John Stultz
2017-08-23 3:01 ` Jisheng Zhang
2017-08-23 3:14 ` John Stultz
2017-08-23 5:37 ` Greg KH
2017-08-23 18:48 ` Rob Herring
2017-08-24 1:44 ` Jisheng Zhang
2017-08-23 5:35 ` Greg KH
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=20170808110305.2748-1-jszhang@marvell.com \
--to=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).