LinuxLists
Users
About
Aniroop Mathur (
[email protected]
)
Number of posts: 36 (0.04 per day)
First post: 2014-12-28 15:57:16
Last post: 2017-04-10 14:40:42
Date
List
Subject
2017-04-10 14:40:42
linux-kernel
Re: Re: Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case
2016-12-14 18:25:09
linux-kernel
Re: [PATCH] Input: evdev: fix queueing of SYN_DROPPED event for EVIOCG[type] IOCTL case
2016-12-04 13:07:14
linux-kernel
Re: [PATCH] Input: mouse: synaptics - change msleep to usleep_range for small msecs
2016-12-03 18:17:27
linux-kernel
Re: [PATCH] Input: touchscreen: edt_ft5x06 - change msleep to usleep_range for small msecs
2016-12-03 17:50:57
linux-kernel
Re: Re: [PATCH] Input: joystick: adi - change msleep to usleep_range for small msecs
2016-12-03 15:43:53
linux-kernel
Re: [PATCH] IIO: Change msleep to usleep_range for small msecs
2016-12-02 19:07:18
linux-kernel
Re: Re: [PATCH] IIO: Change msleep to usleep_range for small msecs
2016-12-02 19:01:22
linux-kernel
Re: [PATCH] IIO: Change msleep to usleep_range for small msecs
2016-11-04 20:58:18
linux-kernel
Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event
2016-10-12 18:36:07
linux-kernel
Re: [PATCH] [v9]Input: evdev: fix bug of dropping valid packet after syn_dropped event
2016-10-04 18:38:44
linux-kernel
Re: [PATCH] [v8]Input: evdev: fix bug of dropping valid packet after syn_dropped event
2016-04-27 14:59:51
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-04-06 20:43:48
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-04-06 19:09:22
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-04-06 14:56:43
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-04-02 17:01:44
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-03-30 17:16:32
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-03-23 19:35:04
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-03-16 18:25:12
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-03-10 18:57:19
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2016-03-09 18:53:40
linux-kernel
Re: [PATCH] Input: Do not add SYN_REPORT in between a single packet data
2015-12-29 18:02:29
linux-kernel
Re: [PATCH] Input: evdev: avoid storing newest SYN_REPORT when dropping all events
2015-12-21 17:23:01
linux-kernel
Re: Ques: [kernel/time/*] Is there any disadvantage in using sleep_range for more than 20ms delay ?
2015-12-14 19:06:45
linux-kernel
Re: Ques: [kernel/time/*] Is there any disadvantage in using sleep_range for more than 20ms delay ?
2015-12-09 16:14:23
linux-kernel
Re: Ques: [kernel/time/*] Is there any disadvantage in using sleep_range for more than 20ms delay ?
2015-12-08 19:21:10
linux-kernel
Re: Ques: [kernel/time/*] Is there any disadvantage in using usleep_range for more than 20ms delay ?
2015-12-08 15:35:16
linux-kernel
Re: Ques: [kernel/time/*] Is there any disadvantage in using sleep_range for more than 20ms delay ?
2015-12-08 02:45:47
linux-kernel
Re: Ques: [kernel/time/*] Is there any disadvantage in using sleep_range for more than 20ms delay ?
2015-12-07 17:59:44
linux-kernel
Ques: [kernel/time/*] Is there any disadvantage in using usleep_range for more than 20ms delay ?
2015-12-07 17:50:10
linux-kernel
Ques: [kernel/time/*] Is there any disadvantage in using sleep_range for more than 20ms delay ?
2014-12-29 17:15:41
linux-kernel
Re: [PATCH] regulator: core: Fix format specifier warning
2014-12-29 17:06:45
linux-kernel
[PATCH] regulator: core: Fix format specifier warning
2014-12-28 16:38:37
linux-kernel
[PATCH] regulator: core: Avoid negative regulator no & initialize it to -1
2014-12-28 16:12:49
linux-kernel
[PATCH] s390: Initialize nr_devices count variable to -1
2014-12-28 16:07:49
linux-kernel
[PATCH] hid: Initialize battery_no to -1 & correct its format string
2014-12-28 15:57:16
linux-kernel
[PATCH] regulator: core: Initialize regulator_no to -1