Searched full:strongly (Results 1 – 25 of 92) sorted by relevance
1234
| /Documentation/devicetree/bindings/mmc/ |
| D | arasan,sdhci.yaml | 52 For this device it is strongly suggested to include
58 For this device it is strongly suggested to include
64 For this device it is strongly suggested to include
68 For this device it is strongly suggested to include
74 For this device it is strongly suggested to include
80 For this device it is strongly suggested to include
86 For this device it is strongly suggested to include
90 For this device it is strongly suggested to include
94 For this device it is strongly suggested to include
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 15 Programs that use these interfaces are strongly encouraged to add their
|
| D | ramoops.rst | 33 memory to be mapped strongly ordered, and atomic operations on strongly ordered
|
| /Documentation/networking/ |
| D | sriov.rst | 7 Modern NICs are strongly encouraged to focus on implementing the ``switchdev``
|
| /Documentation/userspace-api/media/dvb/ |
| D | frontend_legacy_api.rst | 24 kernel due to compatibility issues only. Their usage is strongly not
|
| D | dvbproperty.rst | 112 above example, it is strongly recommended to use
|
| /Documentation/hwmon/ |
| D | shtc1.rst | 59 strongly recommended.
|
| /Documentation/virt/kvm/arm/ |
| D | vcpu-features.rst | 44 It is **strongly recommended** that userspace modify the ID register values
|
| /Documentation/admin-guide/cifs/ |
| D | introduction.rst | 11 the most current dialect) is strongly preferred over using older
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 41 to push back on the proliferation of NVDIMM command sets, so do strongly
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 53 It is strongly recommended to work with the Linux NVMe and block layer
|
| /Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer_mmio.yaml | 41 strongly discouraged; fix your firmware unless absolutely impossible.
|
| D | arm,arch_timer.yaml | 64 strongly discouraged; fix your firmware unless absolutely impossible.
|
| /Documentation/arch/arm64/ |
| D | tagged-pointers.rst | 45 forbidden, and using a non-zero address tag for sp is strongly
|
| /Documentation/ABI/ |
| D | README | 29 strongly encouraged to add their name to the description of
|
| /Documentation/process/ |
| D | contribution-maturity-model.rst | 76 Metrics that are strongly suggested include:
|
| D | security-bugs.rst | 85 As such, the kernel security team strongly recommends that as a reporter
|
| D | volatile-considered-harmful.rst | 88 variables of this type is strongly frowned upon. Jiffies is considered
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 133 fh_to_parent (optional but strongly recommended)
138 get_parent (optional but strongly recommended)
|
| /Documentation/ |
| D | atomic_t.txt | 364 Such implementations are strongly encouraged to add exponential backoff loops
366 also strongly encouraged to inspect/audit the atomic fallbacks, refcount_t and
|
| /Documentation/staging/ |
| D | xz.rst | 61 Using CRC32 is strongly recommended unless there is some other layer
|
| /Documentation/admin-guide/perf/ |
| D | nvidia-pmu.rst | 32 strongly-ordered (SO) PCIE write traffic to local/remote memory. Please see
247 PCIE1 traffic represents strongly ordered (SO) writes.
298 PCIE1 traffic represents strongly ordered (SO) writes.
|
| /Documentation/dev-tools/ |
| D | gpio-sloppy-logic-analyzer.rst | 61 strongly recommended to not use them directly, but to use the script
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 88 even if not caught by other checks, it is strongly recommended that
116 trace, it is strongly recommended that architectures positively identify code
|
| /Documentation/driver-api/usb/ |
| D | callbacks.rst | 85 You are strongly encouraged to use usbcore's facility,
|
1234