On Tue, Jan 27, 2015 at 1:24 AM, Paul Bolle <[email protected]> wrote: > 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 <[email protected]> >> Cc: Elliott Hughes <[email protected]> >> Cc: Todd Poynor <[email protected]> >> Cc: Android Kernel Team <[email protected]> >> Cc: Greg KH <[email protected]> >> Signed-off-by: John Stultz <[email protected]> > > 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 -
Oh grumble. You're right. I'll send a cleanup patch in. Thanks for catching this! -john -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
