Searched full:dependencies (Results  1 – 25 of 172) sorted by relevance
1234567
| /Documentation/kbuild/ | 
| D | Kconfig.select-break | 17 # visit the dependencies of the select target (in this case B).  And since 18 # Kconfig does not visit the dependencies, it breaks the dependencies of B
  | 
| D | kconfig-language.rst | 24 Every entry has its own dependencies. These dependencies are used 44 the config option, input prompt, dependencies, help text and default 72   to the user. Optionally dependencies only for this prompt can be added 90   Optionally, dependencies only for this default value can be added with 119   Optionally dependencies for this default value can be added with "if". 121 - dependencies: "depends on" <expr> 124   dependencies are defined, they are connected with '&&'. Dependencies 137 - reverse dependencies: "select" <symbol> ["if" <expr>] 139   While normal dependencies reduce the upper limit of a symbol (see 140   below), reverse dependencies can be used to force a lower limit of [all …] 
 | 
| /Documentation/admin-guide/ | 
| D | init.rst | 23 4) **Binary exists but dependencies not available**: E.g. required library 24    dependencies of the init binary such as ``/lib/ld-linux.so.2`` missing or 33    library dependencies). And before tackling scripts, better first test a
  | 
| /Documentation/driver-api/ | 
| D | pwrseq.rst | 30     define dependencies in the form of other units that must be enabled before 36     dependencies) that a consumer selects by its name when requesting a handle 66 (units) and define their dependencies. They can then expose named targets that
  | 
| D | dma-buf.rst | 259 Common to all these schemes is that userspace controls the dependencies of these 264 * Only the kernel knows about all DMA fence dependencies, userspace is not aware 265   of dependencies injected due to memory management or scheduler decisions. 267 * Only userspace knows about all dependencies in indefinite fences and when 291 through memory management dependencies which userspace is unaware of, which 294 architecture there is no single entity with knowledge of all dependencies. 297 The only solution to avoid dependencies loops is by not allowing indefinite 364 - Only a fairly theoretical option would be to untangle these dependencies when
  | 
| D | device_link.rst | 7 By default, the driver core only enforces dependencies between devices 13 Sometimes there is a need to represent device dependencies beyond the 18 dependencies, i.e. that one device must be bound to a driver before 25 Device links allow representation of such dependencies in the driver core. 212   dependencies.  It also cannot be used on ACPI systems.
  | 
| /Documentation/RCU/ | 
| D | rcu_dereference.rst | 6 Proper care and feeding of address and data dependencies is critically 9 data dependencies.  These dependencies extend from the rcu_dereference() 15 Most of the time, these dependencies are preserved, permitting you to 20 either address or data dependencies into account it is still possible 23 Follow these rules to preserve the address and data dependencies emanating 53 	trust it to carry dependencies through integer operations. 193 		That said, it is easy to get control dependencies wrong. 194 		Please see the "CONTROL DEPENDENCIES" section of
  | 
| /Documentation/ | 
| D | Kconfig | 9 	  This option makes the Kernel to check for missing dependencies,
  | 
| /Documentation/locking/ | 
| D | lockdep-design.rst | 20 the dependencies between different lock-classes. Lock usage indicates 26 continuing effort to prove lock usages and dependencies are correct or 32 class and hence their usages and dependencies will contribute to those of 156 Furthermore, the following usage based lock dependencies are not allowed 192 Exception: Nested data dependencies leading to nested locking 302 single-task locking dependencies in the kernel as possible, at least 514 Lock dependencies record the orders of the acquisitions of a pair of locks, and 516 dependencies, but we can show that 4 types of lock dependencies are enough for 551 Note that given two locks, they may have multiple dependencies between them, 572 in the path, as the path that doesn't have two conjunct edges (dependencies) as [all …] 
 | 
| /Documentation/gpu/ | 
| D | drm-vm-bind-async.rst | 115 not affect using dma-fences as dependencies for the long-running 124 there are no explicit dependencies. In order to circumvent such a queue-up, a 131 parallel. There may be internal implicit dependencies that only KMD knows 133 to avoid such internal dependencies is to have different VM_BIND 177 implicit dependencies to be fulfilled.
  | 
| /Documentation/livepatch/ | 
| D | cumulative-patches.rst | 5 There might be dependencies between livepatches. If multiple patches need 58   - Decrease user confusion about dependencies between livepatches.
  | 
| /Documentation/devicetree/bindings/timestamp/ | 
| D | hte-consumer.yaml | 29 dependencies:
  | 
| /Documentation/devicetree/bindings/crypto/ | 
| D | ti,omap-sham.yaml | 36 dependencies:
  | 
| /Documentation/devicetree/bindings/nvmem/ | 
| D | nvmem-consumer.yaml | 33 dependencies:
  | 
| /Documentation/bpf/libbpf/ | 
| D | libbpf_build.rst | 6 libelf and zlib are internal dependencies of libbpf and thus are required to link
  | 
| /Documentation/userspace-api/media/mediactl/ | 
| D | media-controller-intro.rst | 24 blocks are shared between different functions, creating dependencies
  | 
| /Documentation/arch/arm/omap/ | 
| D | omap.rst | 9 KERNEL		NEW DEPENDENCIES
  | 
| /Documentation/devicetree/bindings/net/nfc/ | 
| D | nxp,pn532.yaml | 33 dependencies:
  | 
| /Documentation/devicetree/bindings/iio/adc/ | 
| D | sigma-delta-modulator.yaml | 30 dependencies:
  | 
| /Documentation/devicetree/bindings/interrupt-controller/ | 
| D | msi-controller.yaml | 43 dependencies:
  | 
| /Documentation/devicetree/bindings/net/ | 
| D | maxlinear,gpy2xx.yaml | 30 dependencies:
  | 
| /Documentation/devicetree/bindings/gpio/ | 
| D | brcm,xgs-iproc-gpio.yaml | 50 dependencies:
  | 
| /Documentation/translations/zh_TW/admin-guide/ | 
| D | init.rst | 37 4) **二進制存在但依賴項不可用Binary exists but dependencies not available** :
  | 
| /Documentation/translations/zh_CN/admin-guide/ | 
| D | init.rst | 34 4) **二进制存在但依赖项不可用Binary exists but dependencies not available** :
  | 
| /Documentation/dev-tools/kunit/ | 
| D | start.rst | 11 Installing Dependencies 13 KUnit has the same dependencies as the Linux kernel. As long as you can 86 you if you have not included dependencies for the options used. 91    options required to run the desired tests, including their dependencies.
  | 
        1234567