On Tue, 16 Oct 2007, Matthew Garrett wrote:Let's put it in another way: I'd go with Linus suggestion, as it is not icky (although it is a lot more limited in scope than adding a flag to EV_* that could be use for any event, etc). I am not going with the current icky hackery that makes every consumer of EV_* need to know when they are real events, or "notification" events using outside information. It is not "userspace already handles it", even. it is "HAL already handles it", BTW. And unless Dmitry agrees with Linus' suggestion (maybe as a temporary stopgap while something better gets written?), we are not going anywhere, anyway. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| KAMEZAWA Hiroyuki | Re: 2.6.24-rc3-mm1 |
| Ingo Molnar | Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS] |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: Data corruption issue with splice() on 2.6.27.10 |
| Patrick McHardy | Re: [GIT]: Networking |
