Searched refs:treatment (Results 1 – 18 of 18) sorted by relevance
2754 enum reg_request_treatment treatment; in reg_process_hint_user() local2757 if (treatment == REG_REQ_IGNORE || in reg_process_hint_user()2758 treatment == REG_REQ_ALREADY_SET) in reg_process_hint_user()2812 enum reg_request_treatment treatment; in reg_process_hint_driver() local2816 switch (treatment) { in reg_process_hint_driver()2844 if (treatment == REG_REQ_ALREADY_SET) { in reg_process_hint_driver()2915 enum reg_request_treatment treatment; in reg_process_hint_country_ie() local2919 switch (treatment) { in reg_process_hint_country_ie()3033 enum reg_request_treatment treatment; in reg_process_hint() local3061 if (treatment == REG_REQ_IGNORE) in reg_process_hint()[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.
173 /* mark compat w/8572 to get some erratum treatment */
27 treatment in the operating system. For example, avoiding a particular
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.
859 special treatment, this is dealt with in TOOLCHAIN_NEEDS_OLD_ISA_SPEC.
810 also doesn't need a separate treatment.
613 Finally, modifying the contents of the PTE requires special treatment, as the
233 qualifies as regression** which receive priority treatment. Depending on the
507 with any other cgroups and requires special treatment from most
2750 There are a few oddball fences which need special treatment: