Searched refs:treatment (Results 1 – 17 of 17) sorted by relevance
2726 enum reg_request_treatment treatment; in reg_process_hint_user() local2728 treatment = __reg_process_hint_user(user_request); in reg_process_hint_user()2729 if (treatment == REG_REQ_IGNORE || in reg_process_hint_user()2730 treatment == REG_REQ_ALREADY_SET) in reg_process_hint_user()2733 user_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_user()2784 enum reg_request_treatment treatment; in reg_process_hint_driver() local2786 treatment = __reg_process_hint_driver(driver_request); in reg_process_hint_driver()2788 switch (treatment) { in reg_process_hint_driver()2808 driver_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_driver()2816 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
596 special treatment, this is dealt with in TOOLCHAIN_NEEDS_OLD_ISA_SPEC.
363 guarantees the desired differentiated treatment of queues only in
155 treatment will come in later sections.
810 also doesn't need a separate treatment.
463 with any other cgroups and requires special treatment from most
2750 There are a few oddball fences which need special treatment:
