On Tue, 2015-01-20 at 13:42 -0800, John Stultz wrote:
> The functionality provided by the Android alarm-dev driver
> should now be present in the timerfd interface (thanks to
> Greg Hackmann and Todd Poynor).
>
> As of Lollipop, AOSP can make use of the timerfd if
> alarm-dev is not present (though a fixup for setting the
> rtc time if rtc0 isn't the backing for _ALARM clockids has
> been applied post-Lollipop).
>
> Thus, we should be able to remove alarm-dev from staging.
>
> Cc: Greg Hackmann <ghackm...@google.com>
> Cc: Elliott Hughes <e...@google.com>
> Cc: Todd Poynor <toddpoy...@google.com>
> Cc: Android Kernel Team <kernel-t...@android.com>
> Cc: Greg KH <gre...@linuxfoundation.org>
> Signed-off-by: John Stultz <john.stu...@linaro.org>
This became commit 5da41e925656 ("staging: Remove the Android alarm-dev
driver") in today's linux-next (ie, next-20150127). I noticed because a
script I use to check linux-next spotted a minor problem with it.
> drivers/staging/android/Kconfig | 9 -
Here there should have been a line reading
drivers/staging/android/Makefile | 1 -
> drivers/staging/android/alarm-dev.c | 446
> ---------------------------
> drivers/staging/android/android_alarm.h | 41 ---
> drivers/staging/android/uapi/android_alarm.h | 62 ----
> 4 files changed, 558 deletions(-)
> delete mode 100644 drivers/staging/android/alarm-dev.c
> delete mode 100644 drivers/staging/android/android_alarm.h
> delete mode 100644 drivers/staging/android/uapi/android_alarm.h
Is a trivial patch to remove that Makefile line, the one that references
CONFIG_ANDROID_INTF_ALARM_DEV and alarm-dev.o, queued already?
Thanks,
Paul Bolle
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
