Searched refs:treatment (Results 1 – 11 of 11) sorted by relevance
1882 enum reg_request_treatment treatment; in reg_process_hint_user() local1884 treatment = __reg_process_hint_user(user_request); in reg_process_hint_user()1885 if (treatment == REG_REQ_IGNORE || in reg_process_hint_user()1886 treatment == REG_REQ_ALREADY_SET) { in reg_process_hint_user()1888 return treatment; in reg_process_hint_user()1891 user_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_user()1939 enum reg_request_treatment treatment; in reg_process_hint_driver() local1941 treatment = __reg_process_hint_driver(driver_request); in reg_process_hint_driver()1943 switch (treatment) { in reg_process_hint_driver()1948 return treatment; in reg_process_hint_driver()[all …]
19 - KBD_POST_KEYSYM events are sent after the treatment of non-unicode keysyms.
75 The treatment of these regions depends on the type of Zorro space:
74 Vixie cron also seems to have this problem, and needs the same treatment.
173 /* mark compat w/8572 to get some erratum treatment */
217 left fsys-mode, so no special treatment is needed.233 would be the normal & expected behavior, so no special treatment is
23 use of tgid, there is no special treatment for the task that is thread group
91 different from what the kernel remembers, then the treatment is what
171 treatment of cr0.wp=0 below).175 treatment of cr0.wp=0 below).
237 requires special treatment from most controllers. How resource
144 treatment will come in later sections.