Searched full:involves (Results 1 – 25 of 481) sorted by relevance
12345678910>>...20
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | adding-syscalls.rst | 26 - If the new functionality involves operations where the kernel notifies
130 If your new :manpage:`xyzzy(2)` system call involves a filename argument::
150 If your new :manpage:`xyzzy(2)` system call involves a parameter describing an
154 If your new :manpage:`xyzzy(2)` system call involves privileged functionality,
256 way (see below), this involves a "common" entry (for x86_64 and x32) in
314 If the system call involves a structure that is laid out differently on 32-bit
407 This is arch-specific, but typically involves defining assembly entry points
467 involves a new userspace-visible structure, the corresponding header will need
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | adding-syscalls.rst | 26 - If the new functionality involves operations where the kernel notifies
130 If your new :manpage:`xyzzy(2)` system call involves a filename argument::
150 If your new :manpage:`xyzzy(2)` system call involves a parameter describing an
154 If your new :manpage:`xyzzy(2)` system call involves privileged functionality,
256 way (see below), this involves a "common" entry (for x86_64 and x32) in
314 If the system call involves a structure that is laid out differently on 32-bit
407 This is arch-specific, but typically involves defining assembly entry points
467 involves a new userspace-visible structure, the corresponding header will need
|
| /kernel/linux/linux-5.10/arch/powerpc/platforms/embedded6xx/ |
| D | hlwd-pic.c | 27 * Enabling/disabling an interrupt line involves asserting/clearing
28 * the corresponding bit in IMR. ACK'ing a request simply involves
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | pi-futex.rst | 7 - in the user-space fastpath a PI-enabled futex involves no kernel work
79 mutexes involves no kernel work at all - they behave quite similarly to
|
| /kernel/linux/linux-6.6/Documentation/locking/ |
| D | pi-futex.rst | 7 - in the user-space fastpath a PI-enabled futex involves no kernel work
79 mutexes involves no kernel work at all - they behave quite similarly to
|
| /kernel/linux/linux-6.6/arch/powerpc/platforms/embedded6xx/ |
| D | hlwd-pic.c | 27 * Enabling/disabling an interrupt line involves asserting/clearing
28 * the corresponding bit in IMR. ACK'ing a request simply involves
|
| /kernel/linux/linux-5.10/Documentation/ABI/removed/ |
| D | sysfs-bus-nfit | 11 involves determining the ARS capabilities of a given address
|
| /kernel/linux/linux-6.6/Documentation/ABI/removed/ |
| D | sysfs-bus-nfit | 11 involves determining the ARS capabilities of a given address
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/drivers/ |
| D | st-vgxy61.rst | 22 - This involves subtracting the short exposure frame from the long
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-frequency-adf4371 | 23 all the other channels, since it involves changing the VCO
|
| /kernel/linux/linux-6.6/drivers/staging/media/deprecated/atmel/ |
| D | TODO | 4 The move to media controller involves several changes which are
|
| /kernel/linux/linux-5.10/security/selinux/ |
| D | Makefile | 28 # which basically involves adding both headers and a '&' before the colon, see
|
| /kernel/linux/linux-6.6/arch/hexagon/mm/ |
| D | copy_to_user.S | 8 /* The right way to do this involves valignb
|
| D | copy_from_user.S | 9 * The right way to do this involves valignb
|
| /kernel/linux/linux-5.10/arch/hexagon/mm/ |
| D | copy_to_user.S | 8 /* The right way to do this involves valignb
|
| D | copy_from_user.S | 9 * The right way to do this involves valignb
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mailbox/ |
| D | qcom-ipcc.yaml | 14 to route interrupts across various subsystems. It involves a three-level
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/ |
| D | qcom-ipcc.yaml | 14 to route interrupts across various subsystems. It involves a three-level
|
| /kernel/linux/linux-6.6/Documentation/infiniband/ |
| D | opa_vnic.rst | 12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
114 It involves HW resource allocation/management for VNIC functionality.
|
| /kernel/linux/linux-5.10/Documentation/infiniband/ |
| D | opa_vnic.rst | 12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
114 It involves HW resource allocation/management for VNIC functionality.
|
| /kernel/linux/linux-6.6/Documentation/networking/device_drivers/fddi/ |
| D | defza.rst | 30 The board only supports DMA on the receive side. Transmission involves
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_job.h | 26 /* bit set means command submit involves a preamble IB */
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/fddi/ |
| D | defza.rst | 30 The board only supports DMA on the receive side. Transmission involves
|
| /kernel/linux/linux-5.10/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 19 * OPFN involves the communication between two QPs on the HFI
|
| /kernel/linux/linux-6.6/drivers/infiniband/hw/hfi1/ |
| D | opfn.h | 19 * OPFN involves the communication between two QPs on the HFI
|
12345678910>>...20