Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • drivers
  • input
  • input.c
Find file BlameHistoryPermalink
  • Dmitry Torokhov's avatar
    Input: do not pass injected events back to the originating handler · 5fdbe44d
    Dmitry Torokhov authored Nov 08, 2010
    
    
    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: default avatarDmitry Torokhov <dtor@mail.ru>
    5fdbe44d
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7