Searched full:itself (Results 1 – 25 of 589) sorted by relevance
12345678910>>...24
| /Documentation/tools/rv/ |
| D | common_ikm.rst | 12 command itself. If the **rv** command itself generates too many events,
|
| /Documentation/ABI/testing/ |
| D | sysfs-hypervisor-xen | 22 "self" The guest can profile itself
23 "hv" The guest can profile itself and, if it is
25 "all" The guest can profile itself, the hypervisor
|
| D | sysfs-firmware-dmi-entries | 10 The kernel itself does not rely on the majority of the
45 assigned entry handles as the kernel itself makes no
58 entry itself. Note that this is _not the
|
| D | procfs-attr-prev | 11 refers to itself.
|
| D | procfs-attr-current | 11 refers to itself.
|
| D | sysfs-kernel-btf | 17 itself.
|
| D | procfs-attr-exec | 12 refers to itself.
|
| /Documentation/ABI/stable/ |
| D | sysfs-driver-usb-usbtmc | 7 by the device itself. The full description of the bitfields
21 by the device itself. The full description of the bitfields
|
| /Documentation/security/tpm/ |
| D | tpm_ftpm_tee.rst | 19 implemented in firmware. The driver itself doesn't contain much logic and is
22 The firmware itself is based on the following paper:
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 5 used by the firmware itself for configuring the port. From the linux
21 The node contains a number of other properties that are used by the FW itself
|
| /Documentation/filesystems/ext4/ |
| D | verity.rst | 12 stored after the end of the file data itself, in the following format:
38 is encrypted as well as the data itself.
|
| /Documentation/networking/ |
| D | x25.rst | 11 implement LAPB on the card itself, and unintelligent ones that simply do
17 layer of the Linux kernel and therefore it did not concern itself with
|
| /Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 35 irq-flags state, and complains loudly (and turns itself off) if the
48 turn itself off. I.e. the lock validator will still be reliable. There
|
| /Documentation/userspace-api/ |
| D | no_new_privs.rst | 52 - By itself, ``no_new_privs`` can be used to reduce the attack surface
63 dangerous than chroot by itself.
|
| /Documentation/admin-guide/ |
| D | dell_rbu.rst | 16 update itself with the image downloaded in to the memory.
90 to the data file as is without any change to the BIOS image itself.
126 the BIOS knows about the new image downloaded and it updates itself.
|
| /Documentation/hwmon/ |
| D | cros_ec_hwmon.rst | 24 The channel labels exposed via hwmon are retrieved from the EC itself.
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-image-source.rst | 80 processing that requires them, but it does not apply them itself to
86 irrespective of the exact Bayer order of the sensor itself.
|
| /Documentation/sound/soc/ |
| D | jack.rst | 19 together: the jack itself represented by a struct snd_soc_jack, sets of
33 user space. The jack itself is completely passive, it is set up by the
|
| /Documentation/devicetree/bindings/pci/ |
| D | fsl,pci.txt | 13 property. The property itself is treated as a boolean.
|
| /Documentation/devicetree/bindings/net/ |
| D | hisilicon-hns-nic.txt | 27 LAN Switch while the CPU side assume itself have one single NIC connect to
54 ports connected to a LAN Switch while the CPU side assume itself have one
|
| /Documentation/locking/ |
| D | spinlocks.rst | 19 spinlock itself will guarantee the global lock, so it will guarantee that
45 NOTE! The spin-lock is safe only when you **also** use the lock itself
81 itself. The read lock allows many concurrent readers. Anything that
|
| /Documentation/devicetree/bindings/timestamp/ |
| D | hardware-timestamps-common.yaml | 16 itself as a provider with the bindings described in this document.
|
| /Documentation/mm/ |
| D | z3fold.rst | 14 * z3fold doesn't export any API itself and is thus intended to be used
|
| /Documentation/devicetree/bindings/firmware/ |
| D | coreboot.txt | 4 bookkeeping structures to the kernel. Since coreboot itself cannot boot a
|
| /Documentation/devicetree/bindings/iio/ |
| D | common.yaml | 15 sensors. It doesn't constitute a device tree binding specification by itself but
|
12345678910>>...24