RFC staging: alarm-dev: compat_ioctl support
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | staging: alarm-dev: Refactor alarm-dev ioctl code in prep for compat_ioctldrivers/ | +146 | 0 replies | |
| 2/2 | staging: alarm-dev: Implement compat_ioctl supportdrivers/ drivers/ | +67 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/2] staging: alarm-dev: compat_ioctl support
This is a first-pass at implementing compat_ioctl support for Android's alarm-dev driver in staging.
The first patch is some refactoring to cleanup and separate the copying of user data from the logic, and the second patch adds the compat_ioctl support.
As noted in the patch, the only really squirly bit is the handling of ANDROID_ALARM_SET_OLD and ANDROID_ALARM_SET_AND_WAIT_OLD. These are present to support existing older Android applications. Unfortunately these cause ioctl number aliasing issues with the compat ioctls, so on 64bit they are only supported in the compat patch (since any existing android app old enough to use them are likely 32bit).
I'd appreciate feedback from the Android devs on if this is an ok assumption and if it might be reasonable to establish some sort of a phase-out timeline for the _OLD ioctl support.
Any other feedback or thoughts would be welcome!
thanks
-john
John Stultz (2):
staging: alarm-dev: Refactor alarm-dev ioctl code in prep for
compat_ioctl
staging: alarm-dev: Implement compat_ioctl support
drivers/staging/android/alarm-dev.c | 290 +++++++++++++++++++++---------- drivers/staging/android/android_alarm.h | 19 ++ 2 files changed, 213 insertions(+), 96 deletions(-)
Signature · 1 line
1.7.10.4