Searched full:themselves (Results 1 – 25 of 489) sorted by relevance
12345678910>>...20
| /Linux-v5.15/security/landlock/ |
| D | Kconfig | 9 themselves (and their future children) by gradually enforcing
13 configured and enforced by any processes for themselves using the
|
| /Linux-v5.15/include/xen/interface/ |
| D | xenpmu.h | 45 * - XENPMU_MODE_SELF: Guests can profile themselves
46 * - XENPMU_MODE_HV: Guests can profile themselves, dom0 profiles
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-class-devlink | 17 supplier devices themselves are still present.
32 when as long as the supplier and consumer devices themselves
|
| /Linux-v5.15/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 24 Note that pin controllers themselves may also be client devices of themselves.
|
| /Linux-v5.15/Documentation/devicetree/bindings/arc/ |
| D | pct.txt | 9 counted, the HW events themselves cannot serve as a trigger for a sample.
|
| /Linux-v5.15/drivers/misc/ti-st/ |
| D | Kconfig | 15 to register themselves with core and send data, the responses
|
| /Linux-v5.15/Documentation/driver-api/surface_aggregator/clients/ |
| D | index.rst | 7 This is the documentation for client drivers themselves. Refer to
|
| D | cdev.rst | 41 Notifiers themselves do not enable events on the EC. Thus, it may additionally
151 required to receive events, but does not enable events themselves. After a
|
| /Linux-v5.15/drivers/net/ethernet/chelsio/cxgb3/ |
| D | cxgb3_offload.h | 57 * Client registration. Users of T3 driver must register themselves.
155 * The tables themselves are allocated dynamically.
|
| /Linux-v5.15/arch/powerpc/include/asm/ |
| D | exception-64e.h | 14 * critical exceptions which can themselves be interrupted by machine
15 * checks, and since the two later can themselves cause a TLB miss when
|
| /Linux-v5.15/Documentation/trace/ |
| D | stm.rst | 13 trace sources are usually free to pick for themselves any
86 need to allocate that many channels to themselves (via the
|
| /Linux-v5.15/Documentation/userspace-api/ |
| D | landlock.rst | 19 any process, including unprivileged ones, to securely restrict themselves.
183 automatically be composed between themselves according to their runtime parent
275 that may also want to sandbox themselves (e.g. shells, container managers,
|
| /Linux-v5.15/fs/jffs2/ |
| D | LICENCE | 23 files, these files do not by themselves cause the resulting work to be
|
| /Linux-v5.15/arch/sh/kernel/ |
| D | time.c | 26 * Make sure all compiled-in early timers register themselves. in sh_late_time_init()
|
| /Linux-v5.15/kernel/irq/ |
| D | dummychip.c | 16 * Each architecture has to answer this themselves.
|
| /Linux-v5.15/include/uapi/asm-generic/ |
| D | statfs.h | 11 * Special cases can override it for themselves -- except for S390x, which
|
| /Linux-v5.15/drivers/usb/common/ |
| D | Kconfig | 29 attached to them. The ULPI PHY drivers themselves are normal PHY
|
| /Linux-v5.15/tools/perf/Documentation/ |
| D | db-export.txt | 33 4. The export scripts themselves maintain forward compatibility (i.e. an existing
|
| /Linux-v5.15/drivers/gpu/drm/ |
| D | drm_client.c | 147 * Clients cannot initiate a release by themselves. This is done to keep the code simple.
191 * don't need to call this function themselves.
341 * by themselves.
|
| /Linux-v5.15/Documentation/parisc/ |
| D | debugging.rst | 45 at all. Usually Q bit problems will show themselves in unexplainable
|
| /Linux-v5.15/tools/perf/pmu-events/arch/x86/skylakex/ |
| D | uncore-memory.json | 141 … write requests deallocate after being issued to DRAM. Write requests themselves are able to comp…
150 …troller). They deallocate after being issued to DRAM. Write requests themselves are able to comp…
|
| /Linux-v5.15/include/uapi/linux/nfsd/ |
| D | export.h | 49 * subdirectory was a mountpoint, and ignored if they are not themselves
|
| /Linux-v5.15/Documentation/x86/ |
| D | pti.rst | 22 entry/exit functions themselves and the interrupt descriptor table
145 themselves to crash, but they should never crash the kernel.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 95 Always look at the parent devices themselves for determining device
111 not contain any device directories themselves, but only flat lists of
|
| /Linux-v5.15/include/uapi/linux/ |
| D | fsi.h | 14 * HW status information and interpret it themselves, so this
|
12345678910>>...20
