Searched full:concerned (Results 1 – 25 of 35) sorted by relevance
12
| /Documentation/networking/ |
| D | x25.rst | 16 Packet Layer is concerned, the link layer was being performed by a lower
|
| D | sfp-phylink.rst | 33 concerned.
|
| /Documentation/scsi/ |
| D | libsas.rst | 9 layout is as follows: while SCSI Core is concerned with
10 SAM/SPC issues, and a SAS LLDD+sequencer is concerned with
11 phy/OOB/link management, the SAS layer is concerned with:
24 A SAS LLDD is a PCI device driver. It is concerned with
|
| D | scsi_eh.rst | 157 active as long as lower layers are concerned and completion could
|
| /Documentation/devicetree/bindings/mtd/ |
| D | nand-chip.yaml | 18 SPI-NAND devices are concerned by this description.
|
| /Documentation/power/ |
| D | drivers-testing.rst | 44 concerned, it should not matter whether or not the driver is built as a
|
| /Documentation/hwmon/ |
| D | f71882fg.rst | 105 monitoring is concerned.
|
| /Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 100 recurring timers to migrate elsewhere. If you are concerned
185 timers to migrate elsewhere. If you are concerned with multiple
|
| D | module-signing.rst | 57 be marked as being tainted, and the concerned modules will be marked as
|
| /Documentation/virt/kvm/arm/ |
| D | mmio-guard.rst | 15 most graceful as far as the guest is concerned (such as terminating it
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 90 IDE) configurations are concerned, there can only be two devices
|
| /Documentation/filesystems/ |
| D | idmappings.rst | 136 The kernel is mostly concerned with kernel ids. They are used when performing
142 Note that we are only concerned with idmappings as the kernel stores them not
156 going to be concerned with how idmappings are created nor how they are used
344 itself. So we're concerned with what happens when e.g. ``vfs_mkdir()`` is
|
| /Documentation/process/ |
| D | 7.AdvancedTopics.rst | 178 are mostly concerned with coding style and whether code lines have trailing
|
| D | 3.Early-stage.rst | 52 more concerned about system stability, long-term maintenance, and finding
|
| D | maintainer-netdev.rst | 481 of expertise of the reviewers. The reviewers should not be concerned about
|
| D | 2.Process.rst | 406 technical, and participants are not always concerned with showing a high
|
| /Documentation/block/ |
| D | data-integrity.rst | 108 the kernel) is concerned, the integrity metadata is opaque information
|
| /Documentation/filesystems/iomap/ |
| D | design.rst | 393 iomap is concerned:
|
| /Documentation/virt/hyperv/ |
| D | vmbus.rst | 84 ring buffer need not be concerned with ring buffer wrap-around.
|
| /Documentation/sound/cards/ |
| D | audiophile-usb.rst | 177 As far as the Audiophile USB device is concerned, this value let the user
|
| /Documentation/core-api/ |
| D | printk-formats.rst | 312 Where FDDI addresses are concerned the ``F`` specifier can be used after
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 418 recovered filesystem is concerned, there may be many thousands of transactions
696 dirty only the log item cachelines. Normally I wouldn't be concerned about one
|
| /Documentation/arch/arm64/ |
| D | acpi_object_usage.rst | 611 concerned, _OSI is not to be used to determine what
|
| /Documentation/trace/coresight/ |
| D | coresight.rst | 13 document is concerned with the latter.
|
| /Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 27 CPU idle time management is an energy-efficiency feature concerned about using
|
12