Searched refs:treatment (Results 1 – 16 of 16) sorted by relevance
2759 enum reg_request_treatment treatment; in reg_process_hint_user() local2761 treatment = __reg_process_hint_user(user_request); in reg_process_hint_user()2762 if (treatment == REG_REQ_IGNORE || in reg_process_hint_user()2763 treatment == REG_REQ_ALREADY_SET) in reg_process_hint_user()2766 user_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_user()2817 enum reg_request_treatment treatment; in reg_process_hint_driver() local2819 treatment = __reg_process_hint_driver(driver_request); in reg_process_hint_driver()2821 switch (treatment) { in reg_process_hint_driver()2841 driver_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_driver()2849 if (treatment == REG_REQ_ALREADY_SET) { in reg_process_hint_driver()[all …]
22 - KBD_POST_KEYSYM events are sent after the treatment of non-unicode keysyms.
76 The treatment of these regions depends on the type of Zorro space:
77 Vixie cron also seems to have this problem, and needs the same treatment.
27 treatment in the operating system. For example, avoiding a particular
173 /* mark compat w/8572 to get some erratum treatment */
229 left fsys-mode, so no special treatment is needed.245 would be the normal & expected behavior, so no special treatment is
24 use of tgid, there is no special treatment for the task that is thread group
95 different from what the kernel remembers, then the treatment is what
190 treatment of cr0.wp=0 below).194 treatment of cr0.wp=0 below).
388 The only difference in using the DAX in kernel code is the treatment
363 guarantees the desired differentiated treatment of queues only in
155 treatment will come in later sections.
815 also doesn't need a separate treatment.
2556 There are a few oddball fences which need special treatment:
463 with any other cgroups and requires special treatment from most
