Searched refs:awaken (Results 1 – 13 of 13) sorted by relevance
428 int ret, awaken; in __key_instantiate_and_link() local433 awaken = 0; in __key_instantiate_and_link()449 awaken = 1; in __key_instantiate_and_link()473 if (awaken) in __key_instantiate_and_link()573 int ret, awaken, link_ret = 0; in key_reject_and_link() local578 awaken = 0; in key_reject_and_link()599 awaken = 1; in key_reject_and_link()618 if (awaken) in key_reject_and_link()
155 bool awaken:1; member
111 evo_data(push, asyw->ntfy.awaken << 30 | asyw->ntfy.offset); in ovly507e_ntfy_set()
131 evo_data(push, asyw->ntfy.awaken << 30 | asyw->ntfy.offset); in base507c_ntfy_set()
138 evo_data(push, asyw->ntfy.offset | asyw->ntfy.awaken); in wndwc37e_ntfy_set()
170 asyw->ntfy.awaken = false; in nv50_wndw_ntfy_enable()
718 bool awaken = false; in __fscache_disable_cookie() local758 awaken = true; in __fscache_disable_cookie()761 if (awaken) in __fscache_disable_cookie()
709 bool awaken = false; in fscache_drop_object() local728 awaken = true; in fscache_drop_object()731 if (awaken) in fscache_drop_object()
44 (only to be awaken quite soon)
152 to be awaken for these requests. Sleeping VCPUs will handle the153 requests when they are awaken later for some other reason.284 to check if it should awaken. One reason to do so is to provide
188 allocation request will awaken the ``kswapd`` daemon. It will
185 a timer will awaken these CPUs every four jiffies in order to ensure
3555 awaken the corresponding "rcuoN" kthreads,
