Searched full:assumption (Results 1 – 25 of 49) sorted by relevance
12
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 19 speculatively allocates 8KiB of disk space to the file on the assumption
39 same block group as the directory, when feasible. The working assumption
|
| /Documentation/networking/ |
| D | phy-link-topology.rst | 16 through the legacy ioctls and the ethtool netlink commands. The base assumption
28 This assumption falls apart in more complex topologies that can arise when,
|
| /Documentation/devicetree/bindings/regulator/ |
| D | gpio-regulator.yaml | 79 assumption is false.
|
| D | pwm-regulator.yaml | 31 make an assumption that a %50 duty-cycle value will cause the regulator
|
| D | fixed-regulator.yaml | 104 assumption is false.
|
| /Documentation/driver-api/ |
| D | pps.rst | 52 This implies that the source has a /dev/... entry. This assumption is
55 task for a PPS API. But this assumption does not work for a single
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | divider.txt | 13 This assumption may be modified by the following optional properties:
|
| /Documentation/driver-api/cxl/ |
| D | access-coordinates.rst | 22 iterated in the same iteration loop. The assumption is made that subtle
|
| /Documentation/mm/damon/ |
| D | design.rst | 193 assumption (pages in a region have the same access frequencies) is kept, only
203 assumption is not guaranteed.
210 fulfill the assumption (pages in same region have similar access frequencies),
212 monitoring quality. To keep the assumption as much as possible, DAMON
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 114 the adapter's functionality mask, since the assumption is
|
| D | i2c-topology.rst | 175 of another mux, this might break a possible assumption from the
270 But if M2 is not making the above stated assumption, and if M2 is not
|
| /Documentation/arch/x86/ |
| D | kernel-stacks.rst | 64 If that assumption is ever broken then the stacks will become corrupt.
|
| D | mds.rst | 51 exception. The rationale behind this assumption is that the code construct
|
| /Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 14 the bootloader, with the assumption that the display hardware has
|
| /Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 95 restarted. Hot-chaining doesn't break the assumption that
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 158 is nothing to be done. In particular, there is the implicit assumption
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 213 on the assumption that they will be able to avoid serious integration
|
| D | 6.Followthrough.rst | 188 it with the assumption that you will not be around to maintain it
|
| /Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 251 right for the CPUs or not (due to the above assumption that physical CPU
|
| /Documentation/staging/ |
| D | lzo.rst | 75 are called under the assumption that a certain number of bytes follow
|
| /Documentation/security/tpm/ |
| D | tpm-security.rst | 183 based attestation process. The assumption here is that the
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 263 assumption can lead to unreliable stack traces. For example, consider the
|
| /Documentation/scheduler/ |
| D | sched-bwc.rst | 59 \Sum e_i; that is, there is a bounded tardiness (under the assumption
|
| /Documentation/arch/arm64/ |
| D | arm-acpi.rst | 289 and the drivers need to take them into account. In ACPI, the assumption
420 ACPI makes the assumption that clocks are initialized by the firmware --
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 279 implementation assumes that directory graph is a tree. This assumption is
|
12