Searched refs:treatment (Results 1 – 15 of 15) sorted by relevance
2389 enum reg_request_treatment treatment; in reg_process_hint_user() local2391 treatment = __reg_process_hint_user(user_request); in reg_process_hint_user()2392 if (treatment == REG_REQ_IGNORE || in reg_process_hint_user()2393 treatment == REG_REQ_ALREADY_SET) in reg_process_hint_user()2396 user_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_user()2446 enum reg_request_treatment treatment; in reg_process_hint_driver() local2448 treatment = __reg_process_hint_driver(driver_request); in reg_process_hint_driver()2450 switch (treatment) { in reg_process_hint_driver()2467 driver_request->intersect = treatment == REG_REQ_INTERSECT; in reg_process_hint_driver()2475 if (treatment == REG_REQ_ALREADY_SET) { in reg_process_hint_driver()[all …]
21 - 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.
23 treatment in the operating system. For example, avoiding a particular
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
95 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).
380 The only difference in using the DAX in kernel code is the treatment
342 guarantees the desired differentiated treatment of queues only in
160 treatment will come in later sections.
428 with any other cgroups and requires special treatment from most
1816 There are a few oddball fences which need special treatment:
