From 982ad74c9534f447b2ad6d0a1a43aaac873326f7 Mon Sep 17 00:00:00 2001 From: John Stultz Date: Wed, 10 Aug 2011 11:40:23 -0700 Subject: [PATCH] --- yaml --- r: 269184 b: refs/heads/master c: d77e23accec56bf2ba12187fe77a2f500a511282 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/kernel/time/alarmtimer.c | 9 --------- 2 files changed, 1 insertion(+), 10 deletions(-) diff --git a/[refs] b/[refs] index 140fde7e5daa..a362a65423a6 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: dce75a8c71819ed4c7efdcd53c9b6f6356dc8cb5 +refs/heads/master: d77e23accec56bf2ba12187fe77a2f500a511282 diff --git a/trunk/kernel/time/alarmtimer.c b/trunk/kernel/time/alarmtimer.c index f03b04291b6f..a522c007e6fd 100644 --- a/trunk/kernel/time/alarmtimer.c +++ b/trunk/kernel/time/alarmtimer.c @@ -525,15 +525,6 @@ static int alarm_timer_set(struct k_itimer *timr, int flags, if (!rtcdev) return -ENOTSUPP; - /* - * XXX HACK! Currently we can DOS a system if the interval - * period on alarmtimers is too small. Cap the interval here - * to 100us and solve this properly in a future patch! -jstultz - */ - if ((new_setting->it_interval.tv_sec == 0) && - (new_setting->it_interval.tv_nsec < 100000)) - new_setting->it_interval.tv_nsec = 100000; - if (old_setting) alarm_timer_get(timr, old_setting);