From: John Stultz <john.stultz@linaro.org>
To: Arnd Bergmann <arnd.bergmann@linaro.org>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
"Colin Cross" <ccross@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Serban Constantinescu" <serban.constantinescu@arm.com>,
"Android Kernel Team" <kernel-team@android.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [RFC][PATCH] staging: Fix build issues with new binder API
Date: Thu, 27 Feb 2014 11:20:33 -0800 [thread overview]
Message-ID: <530F9001.8040608@linaro.org> (raw)
In-Reply-To: <201402272015.24077.arnd.bergmann@linaro.org>
On 02/27/2014 11:15 AM, Arnd Bergmann wrote:
> On Wednesday 26 February 2014, John Stultz wrote:
>> The new 64bit binder API causes build issues on 32bit ARM
>> due to the lack of 64bit __get_user_asm_* implementation.
> It is impossible to implement this. Many have tried before.
>
>> Until that implementation is done, remove the choice for
>> 32bit ARM, automatically enabling the old 32bit binder
>> protocol.
>>
>> This can be reverted once a 64bit __get_user_asm_*
>> implementation is merged.
> I think the best solution is to use __copy_from_user for
> the 64-bit access. You can wrap it in a helper function
> if you want to speed up the native-word-size case.
Ah. Thanks for the context and the tip. Will try to get an appropriate
solution there then.
thanks
-john
prev parent reply other threads:[~2014-02-27 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 22:29 [RFC][PATCH] staging: Fix build issues with new binder API John Stultz
2014-02-27 3:34 ` Greg KH
2014-02-27 19:04 ` John Stultz
2014-02-27 19:12 ` Greg KH
[not found] ` <530E6B56.8060405@linaro.org>
2014-02-27 19:15 ` Fwd: " Arnd Bergmann
2014-02-27 19:20 ` John Stultz [this message]
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=530F9001.8040608@linaro.org \
--to=john.stultz@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=arve@android.com \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serban.constantinescu@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.