Searched full:necessarily (Results 1 – 25 of 113) sorted by relevance
12345
| /Documentation/userspace-api/media/dvb/ |
| D | legacy_dvb_apis.rst | 16 The APIs described here doesn't necessarily reflect the current
|
| /Documentation/filesystems/ext4/ |
| D | bitmaps.rst | 18 necessarily the case that no blocks are in use -- if ``meta_bg`` is set,
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-gpio | 28 /label ... (r/o) descriptive, not necessarily unique
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 16 displays. They are typically but not necessarily implemented using a white
|
| /Documentation/userspace-api/media/v4l/ |
| D | rw.rst | 17 to or from user memory, so this I/O method is not necessarily less
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-css | 29 layer (this implies that this attribute is not necessarily
|
| D | sysfs-kernel-iommu_groups | 21 regions that are reserved. Not necessarily all
|
| D | sysfs-bus-wmi | 38 compatible WMI drivers. This GUID is not necessarily unique
|
| D | sysfs-secvar | 79 This is not necessarily the same as the max size that can be
|
| D | dev-kmsg | 112 lines are not necessarily correct, and the stream could be
|
| D | sysfs-ptp | 25 MAC based ones. The string does not necessarily have
|
| /Documentation/driver-api/ |
| D | spi.rst | 20 to support implementing SPI slaves would necessarily look different.)
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 17 It doesn't necessarily provide a user space application with semantics
|
| D | efi-stub.rst | 39 should be copied but not necessarily renamed.
|
| /Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 33 necessarily before initial posting. Contact the list if you need help
|
| /Documentation/arch/riscv/ |
| D | uabi.rst | 61 Inversely, the absence of an extension in these lines does not necessarily mean
|
| /Documentation/filesystems/ |
| D | ntfs3.rst | 115 which is not necessarily as effective as JBD would be.
|
| /Documentation/arch/powerpc/ |
| D | ptrace.rst | 82 A request specifies one event, not necessarily just one register to be set.
|
| D | elf_hwcaps.rst | 40 Software that targets a particular platform does not necessarily have to
|
| /Documentation/driver-api/driver-model/ |
| D | overview.rst | 58 Note also that that struct device dev is not necessarily defined at the
|
| /Documentation/trace/rv/ |
| D | da_monitor_instrumentation.rst | 55 does not necessarily need to use them: they are just starting points.
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 109 driving the shared signal low. That's not necessarily an error. As one common
|
| /Documentation/hwmon/ |
| D | ltc4282.rst | 115 even if some failure is detected in these logs, it does necessarily mean
|
| /Documentation/arch/arm/pxa/ |
| D | mfp.rst | 43 NOTE: the external pad is named as MFP_PIN_GPIO19, it doesn't necessarily
140 and on which edge(s). This, however, doesn't necessarily mean the
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 116 additional engines, but they don't necessarily need to be describe in the
|
12345