From: John Stultz <john.stultz@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.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>,
"Arnd Bergmann" <arnd.bergmann@linaro.org>
Subject: Re: [RFC][PATCH] staging: Fix build issues with new binder API
Date: Thu, 27 Feb 2014 11:04:01 -0800 [thread overview]
Message-ID: <530F8C21.9070602@linaro.org> (raw)
In-Reply-To: <20140227033400.GA31199@kroah.com>
On 02/26/2014 07:34 PM, Greg KH wrote:
> On Wed, Feb 26, 2014 at 02:29:07PM -0800, John Stultz wrote:
>> The new 64bit binder API causes build issues on 32bit ARM
>> due to the lack of 64bit __get_user_asm_* implementation.
> So no one ever tested this out on ARM? Really, that seems odd...
Its my bad, I was focused on the 32bit legacy compatibility code in my
testing because the userspace I have only works with that.
Arve actually warned about this in one of his mails, but I mistakenly
thought it was an issue w/ 3.10 and earlier kernels and had since been
addressed.
> Anyway, if you want this to always be on, that's fine with me, your
> choice :)
I think its the best option for now, but wanted to send it out for
comment to see if anyone objected.
I'm about to head for a conference so I'll be offline until around
Monday. While at the conference I'm going to be working with folks to
see if we can't get the real solution (a __get_user_asm_64
implementation) sorted. But if there are no objections, it might be
best to queue this for staging-next so folks don't hit the issue in the
meantime.
thanks
-john
next prev parent reply other threads:[~2014-02-27 19:04 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 [this message]
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
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=530F8C21.9070602@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox