Searched refs:conclusion (Results 1 – 7 of 7) sorted by relevance
| /linux/drivers/md/dm-vdo/ |
| H A D | action-manager.c | 33 vdo_action_conclusion_fn conclusion; member
215 action->conclusion = no_conclusion; in launch_current_action()
266 result = action.conclusion(manager->context); in finish_action_callback()
294 vdo_zone_action_fn action, vdo_action_conclusion_fn conclusion, in vdo_schedule_action() argument
298 action, conclusion, parent); in vdo_schedule_action()
323 vdo_action_conclusion_fn conclusion, in vdo_schedule_operation() argument
327 conclusion, NULL, parent); in vdo_schedule_operation()
355 vdo_action_conclusion_fn conclusion, in vdo_schedule_operation_with_context() argument
378 .conclusion = (conclusion == NULL) ? no_conclusion : conclusion, in vdo_schedule_operation_with_context()
|
| H A D | action-manager.h | 94 vdo_zone_action_fn action, vdo_action_conclusion_fn conclusion,
100 vdo_action_conclusion_fn conclusion,
107 vdo_action_conclusion_fn conclusion,
|
| /linux/Documentation/timers/ |
| H A D | hrtimers.rst | 12 conclusion that the timer wheel code is fundamentally not suitable for
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| H A D | ssh.rst | 343 In conclusion, this suggests a limit of at most one pending un-ACKed frame
|
| /linux/Documentation/hwmon/ |
| H A D | w83781d.rst | 445 As a conclusion, you can write 0x00 or 0x8F to the PWM registers to make
|
| /linux/Documentation/input/devices/ |
| H A D | atarikbd.rst | 447 will still be transmitted to conclusion and then the PAUSE will take effect.
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 631 Moreover, we can have a similar conclusion for L2's holder: it has to wait L3's
|