Searched full:furthermore (Results 1 – 25 of 520) sorted by relevance
12345678910>>...21
| /kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlx5/core/en/xsk/ |
| D | rx.c | 42 * DMA address point directly to the necessary place. Furthermore, in in mlx5e_xsk_skb_from_cqe_mpwrq_linear()
88 * DMA address point directly to the necessary place. Furthermore, the in mlx5e_xsk_skb_from_cqe_linear()
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | rbtree_types.h | 23 * Furthermore, users that want to cache both pointers may
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | kernel_mode_neon.rst | 23 required. Furthermore, special care is required for code that may sleep [i.e.,
83 between calls to these respective functions. Furthermore, GCC may generate NEON
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/ |
| D | kernel_mode_neon.rst | 23 required. Furthermore, special care is required for code that may sleep [i.e.,
83 between calls to these respective functions. Furthermore, GCC may generate NEON
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,vf610-mscm-ir.txt | 5 allows to configure the recipient of each peripheral interrupt. Furthermore
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/freescale/ |
| D | fsl,vf610-mscm-ir.txt | 5 allows to configure the recipient of each peripheral interrupt. Furthermore
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | querycap.rst | 10 are equally applicable to all types of devices. Furthermore devices of
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | querycap.rst | 10 are equally applicable to all types of devices. Furthermore devices of
|
| /kernel/linux/linux-6.6/tools/arch/sparc/include/asm/ |
| D | barrier_64.h | 36 * and furthermore most sparc64 chips implement more stringent
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra124-dpaux-padctl.txt | 22 Furthermore, given that the pad functions are only applicable to a
|
| /kernel/linux/linux-5.10/tools/arch/sparc/include/asm/ |
| D | barrier_64.h | 36 * and furthermore most sparc64 chips implement more stringent
|
| /kernel/linux/linux-6.6/Documentation/driver-api/usb/ |
| D | persist.rst | 133 Furthermore, the USB-persist feature applies to _all_ USB devices, not
153 Furthermore it's quite possible to leave a USB device exactly the same
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | persist.rst | 133 Furthermore, the USB-persist feature applies to _all_ USB devices, not
153 Furthermore it's quite possible to leave a USB device exactly the same
|
| /kernel/linux/linux-6.6/Documentation/gpu/rfc/ |
| D | i915_vm_bind.h | 108 * are not ordered. Furthermore, parts of the VM_BIND operation can be done
173 * are not ordered. Furthermore, parts of the VM_UNBIND operation can be done
|
| /kernel/linux/linux-5.10/tools/hv/ |
| D | hv_set_ifconfig.sh | 45 # configured for the interface. Furthermore, the configuration
|
| /kernel/linux/linux-6.6/arch/sparc/include/asm/ |
| D | barrier_64.h | 34 * and furthermore most sparc64 chips implement more stringent
|
| /kernel/linux/linux-5.10/arch/sparc/include/asm/ |
| D | barrier_64.h | 34 * and furthermore most sparc64 chips implement more stringent
|
| /kernel/linux/linux-6.6/Documentation/locking/ |
| D | ww-mutex-design.rst | 66 acquire context. Furthermore the acquire context keeps track of debugging state
74 Furthermore there are three different class of w/w lock acquire functions:
136 Furthermore the lock helper can use propagate the -EALREADY return code back to
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | ww-mutex-design.rst | 66 acquire context. Furthermore the acquire context keeps track of debugging state
74 Furthermore there are three different class of w/w lock acquire functions:
136 Furthermore the lock helper can use propagate the -EALREADY return code back to
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | examples.txt | 65 Furthermore, these tracepoints can be used to sample the workload as
119 Furthermore, call-graph sampling can be done too, of page
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | examples.txt | 65 Furthermore, these tracepoints can be used to sample the workload as
119 Furthermore, call-graph sampling can be done too, of page
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | vf610-nfc.txt | 16 clock are found in the SoC hardware reference manual. Furthermore,
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mtd/ |
| D | vf610-nfc.txt | 16 clock are found in the SoC hardware reference manual. Furthermore,
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,cpu-intc.txt | 39 Furthermore, this interrupt-controller MUST be embedded inside the cpu
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,cpu-intc.txt | 39 Furthermore, this interrupt-controller MUST be embedded inside the cpu
|
12345678910>>...21