[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB0TPYG-Q6Ki_FMM1u+i_g+0ykQgeUTRpm00qycAUVQOqVH6eQ@mail.gmail.com>
Date: Fri, 11 May 2018 09:57:52 +0200
From: Martijn Coenen <maco@...roid.com>
To: kbuild test robot <lkp@...el.com>,
Greg KH <gregkh@...uxfoundation.org>
Cc: kbuild-all@...org, John Stultz <john.stultz@...aro.org>,
Todd Kjos <tkjos@...gle.com>,
Arve Hjønnevåg <arve@...roid.com>,
Amit Pundir <amit.pundir@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
LKML <linux-kernel@...r.kernel.org>,
"open list:ANDROID DRIVERS" <devel@...verdev.osuosl.org>,
Martijn Coenen <maco@...gle.com>
Subject: Re: [PATCH] ANDROID: binder: remove 32-bit binder interface.
On Sat, May 5, 2018 at 2:10 PM, kbuild test robot <lkp@...el.com> wrote:
> drivers/android/binder.o: In function `binder_thread_write':
>>> binder.c:(.text+0x6a16): undefined reference to `__get_user_bad'
Looks like m68k doesn't support 64-bit get_user(). I could just have
binder depend on !CONFIG_M68K, but there may be other architectures
still that don't support this. Another alternative would be to
whitelist the architectures Android supports - eg arm, arm64, x86,
x86_64. But I'm not sure if arch-limited drivers are considered bad
form. Does anybody have suggestions for how to deal with this?
Thanks,
Martijn
> binder.c:(.text+0x6c9a): undefined reference to `__get_user_bad'
> binder.c:(.text+0x701e): undefined reference to `__get_user_bad'
> binder.c:(.text+0x7414): undefined reference to `__get_user_bad'
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
Powered by blists - more mailing lists