Home
last modified time | relevance | path

Searched refs:can_attach (Results 1 – 7 of 7) sorted by relevance

/linux/drivers/usb/gadget/function/
H A Du_tcm.h24 * @can_attach: true a function can be bound to gadget
33 bool can_attach; member
/linux/drivers/usb/gadget/legacy/
H A Dtcm_usb_gadget.c153 tcm_opts->can_attach = true; in usb_target_gadget_init()
/linux/Documentation/admin-guide/cgroup-v1/
H A Dcgroups.rst594 ``int can_attach(struct cgroup *cgrp, struct cgroup_taskset *tset)``
632 Called when a task attach operation has failed after can_attach() has succeeded.
633 A subsystem whose can_attach() has some side-effects should provide this
635 This will be called only about subsystems whose can_attach() operation have
636 succeeded. The parameters are identical to can_attach().
643 The parameters are identical to can_attach().
/linux/include/linux/
H A Dcgroup-defs.h746 int (*can_attach)(struct cgroup_taskset *tset); member
/linux/kernel/cgroup/
H A Dpids.c452 .can_attach = pids_can_attach,
H A Dcgroup.c2607 * This function fails iff one of the ->can_attach callbacks fails and
2622 if (ss->can_attach) { in cgroup_migrate_execute()
2624 ret = ss->can_attach(tset); in cgroup_migrate_execute()
2902 * As long as a controller's ->can_attach() doesn't fail, this function is
2903 * guaranteed to succeed. This means that, excluding ->can_attach()
H A Dcpuset.c3127 * can_attach beforehand should guarantee that this doesn't in cpuset_attach_task()
3726 .can_attach = cpuset_can_attach,