| commit | 5fdbe44d033d059cc56c2803e6b4dbd8cb4e5e39 | |
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | |
| Tue, 9 Nov 2010 05:51:25 +0000 (8 21:51 -0800) | ||
| committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | |
| Thu, 11 Nov 2010 09:01:26 +0000 (11 01:01 -0800) | ||
| tree | 18dcde03df9d44a7e91a20472449f1f95b57da25 | treesnapshot (tar.gz zip) |
| parent | 17d01f28e160f8a9c9ecda2e335d0047ec9e7388 | commitdiff |
Input: do not pass injected events back to the originating handler
Sometimes input handlers (as opposed to input devices) have a need to
inject (or re-inject) events back into input core. For example sysrq
filter may want to inject previously suppressed Alt-SysRq so that user
can take a screen print. In this case we do not want to pass such events
back to the same same handler that injected them to avoid loops.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Sometimes input handlers (as opposed to input devices) have a need to
inject (or re-inject) events back into input core. For example sysrq
filter may want to inject previously suppressed Alt-SysRq so that user
can take a screen print. In this case we do not want to pass such events
back to the same same handler that injected them to avoid loops.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
| drivers/input/input.c | diffblobblamehistory |